Pfrv3 Work Flow Guide

7/24/2019 Pfrv3 Work Flow Guide

1/113

1

Performance Routing version 3 for IOS-XE release

Workflow and Operation Guide

Version:

1.0 November 2014

PfR allows network administrators to minimize bandwidth

cost, enable intelligent load distribution, improve application

performance, and deploy dynamic failure detection at the

WAN access edge. Cisco IOS/IOS-XE PfR makes real-time

routing adjustments based on the criteria other than static

routing metrics such as delay, packet loss, jitter, path

availability, and traffic load distribution.


2/113

2

Contents

1 What is PfRv3? ........................................................................................................................................................ 3

2 Enterprise Domain Topology .................................................................................................................................. 4

3 Enterprise Domain Provisioning ............................................................................................................................. 5

3.1 Device Setup and Role ..................................................................................................................................... 5

3.2 Hub Master Controller (MC)............................................................................................................................ 5

3.3 Hub Border Routers (BR1 and BR2) ................................................................................................................. 6

3.4 Branch Routers ................................................................................................................................................ 8

4 Defining Domain Policies ...................................................................................................................................... 11

5 Checking Domain Discovery ................................................................................................................................. 13

5.1 Check Hub MC status .................................................................................................................................... 13

5.2 Check Hub BR Status ..................................................................................................................................... 15

5.3 Check Hub Discovered sites .......................................................................................................................... 18

5.4 Check Branch MC Status ............................................................................................................................... 19

5.5 Check Branch BR Status ................................................................................................................................. 215.6 Check Unified Performance Monitor ............................................................................................................ 23

6 Monitoring Operation ........................................................................................................................................... 32

6.1 Monitor Site Prefix ........................................................................................................................................ 32

6.2 Monitor Traffic Class ..................................................................................................................................... 35

6.3 Monitor Channels .......................................................................................................................................... 48

7 Troubleshooting.................................................................................................................................................... 66

7.1 Platform CLI ................................................................................................................................................... 66

7.2 Conditional Debug ......................................................................................................................................... 75

7.3 Packet Trace .................................................................................................................................................. 79

7.4 Embedded Packet Capture (EPC) .................................................................................................................. 90

8 Configuration Sample ........................................................................................................................................... 92

8.1 Example configuration on Hub MC ............................................................................................................... 92

8.2 Example configuration on Hub BR1............................................................................................................... 94

8.3 Example configuration on Hub BR2............................................................................................................... 99

8.4 Example configuration on Branch10(R10) .................................................................................................. 103

8.5 Example configuration on Branch11(R11) .................................................................................................. 108


3/113

3

1 What is PfRv3?

PfR v3 is the evolution of Performance Routing (PfR). It is a one-touch provisioning and multisite coordinationsolution that simplifies network provisioning. PfRv3 is an DSCP and application-based policy framework that

provides a multi-site aware bandwidth and path control optimization for WAN and cloud-based applications. It is

integrated with existing AVC components such as Performance Monitoring, QoS, and NBAR2. This is extremely

useful for enterprise and managed service providers who are looking for methods to increase the WAN reliability

and availability while saving cost.


4/113

4

2

Enterprise Domain Topology

The typical IWAN topology includes a central site called the IWAN Hub and several branch sites. A

branch site can include a single CPE or dual CPEs.

Intelligent Path Control using Cisco Performance Routing (PfR) improves application delivery and WAN

efficiency. PfR enables intelligence of Cisco IOS routers to improve application performance and

availability. PfR allows customers to protect critical applications from fluctuating WAN performance

while intelligently load balancing traffic over all WAN paths. PfR monitors network performance and

selects the best path for each application based on advanced criteria such as reachability, delay, jitter

and loss.

In this workflow, we focus on the step-by-step workflow guide for PfRv3 provision, operation andtroubleshooting on IOS-XE platforms. Basic VPN configuration is not covered in this document, for more

information about VPN WAN Design configuration, see the latestCisco Validated Designs for Enterprise

WAN.
http://www.cisco.com/c/en/us/solutions/enterprise/design-zone-branch-wan/cvd_ent_wan.htmlhttp://www.cisco.com/c/en/us/solutions/enterprise/design-zone-branch-wan/cvd_ent_wan.htmlhttp://www.cisco.com/c/en/us/solutions/enterprise/design-zone-branch-wan/cvd_ent_wan.htmlhttp://www.cisco.com/c/en/us/solutions/enterprise/design-zone-branch-wan/cvd_ent_wan.htmlhttp://www.cisco.com/c/en/us/solutions/enterprise/design-zone-branch-wan/cvd_ent_wan.htmlhttp://www.cisco.com/c/en/us/solutions/enterprise/design-zone-branch-wan/cvd_ent_wan.html


5/113

5

3

Enterprise Domain Provisioning

3.1 Device Setup and Role

There are four different roles a device can play in PfRv3 configuration:

Hub Master Controller (Hub MC)- The master controller at the hub site, which can be either a

data center or a head quarter. All policies are configured on the hub MC. It acts as master

controller for the site and makes optimization decision.

Hub Border Router (Hub BR)- The border controller at the hub site. WAN interface terminates

in the hub border routers. PfRv3 is enabled on these interfaces. You can configure more than

one WAN interface on the same device. You can have multiple hub border devices.

Branch Master Controller (Branch MC)- The branch master controller is the master controller

at the branch site. There is no policy configuration on this device. It receives policy from the hub

MC. This device acts as master controller for that site for making optimization decision.

Branch Border Router (Branch BR)- The border device at the branch site. There is no

configuration other than enabling of PfRv3 border MC on the device. The WAN interface that

terminates on the device is detected automatically.

In general, Hub Master Controller like CSR1000v or ASR1002x router with 8G/16G DRAM memory size,

and RP2/ESP100, RP2/ESP200 as Hub Border Router can support up to 2000 branch sites deployment.

On the branch site, ISR G2 or ISR4400/4300 Series Router can be deployed depending on performance

requirements.

3.2 Hub Master Controller (Hub MC)

The hub master controller is the master controller at the hub site (Datacenter1 is our deployment

example; we focus on one DC only). This is the device where all policies are configured. It also acts as

master controller for that site and makes optimization decision. It is important to note that the Hub MC

is NOT a centralized Master Controller for all Border Routers on all sites. This is the central point of

provisioning for the entire Enterprise Domain.

In this deployment example, IWAN POP is the primary datacenter and MC is configured as the Hub MC.

!i nter f ace Loopback0i p addr ess 10. 8. 3. 3 255. 255. 255. 255

!

domai n onevrf def aul tmast er hubsour ce- i nter f ace Loopback0ent erpri se- pr ef i x pr ef i x- l i st ENTERPRI SEsi t e- pr ef i xes pr ef i x- l i st DATA_CENTER_1

!i p pr ef i x- l i st DATA_CENTER_1 seq 5 permi t 10. 8. 0. 0/ 16 l e 24i p pr ef i x- l i st ENTERPRI SE seq 5 permi t 10. 0. 0. 0/ 8 l e 24


6/113

6

!

Notes:

Site-prefix prefix-list define static site-prefix for local-site, and this disable automatic site-prefix

learning on the border router;

Static site-prefixes prefix-list is only required for transit sites like DMVPN Hub site for spoke tospoke traffic which disable Automatic prefix learn;

Enterprise-prefix prefix-list define the boundary for all inside enterprise prefix; any prefix out

range of these prefix-list and not advertised by any remote sites are considered as internet

prefix, and should be controlled and routed over internet-bound links;

EIGRP SAF auto-configuration enabled and unicast-listen request from remote site when domain

hub master configured.

3.3

Hub Border Routers ( Hub BR1 and BR2)

A Hub Border Router is a border controller at the hub site. This is the device where WAN interface

terminates. PfR is enabled on these interfaces. There could be one or more WAN interface on the same

device. There can be one or more Hub BRs.

On the Hub Border Routers, PfR must be configured with:

The source-interface of local border router

The address of the local MC

The path name on external interfaces

The border routers on the central site register to the central MC with their external interface definition

together with their path names. You can use the global routing table (default VRF) or define specific

VRFs for hub border routers.

BR1 example configuration:


!domai n onevrf def aul tbordersour ce- i nter f ace Loopback0mast er 10. 8. 3. 3

!!i nter f ace Tunnel 100bandwidth 100000i p addr ess 10. 0. 100. 84 255. 255. 255. 0no i p redi r ectsi p mt u 1400i p nhr p aut hent i cat i on ci scoi p nhr p map mul t i cast dynami c


7/113

7

i p nhr p net work- i d 1i p nhr p hol dt i me 600i p t cp adj ust - mss 1360l oad- i nt er val 30t unnel sour ce Gi gabi t Et hernet 3t unnel mode gr e mul t i poi ntt unnel key 100t unnel pr otect i on i psec pr of i l e DMVPN- PROFI LE1

domai n onepath MPLS!

Notes:

When config path name, there are two kinds of external interfaces, one is enterprise link by

default which is normally a DMVPN Tunnel overlay interface connected with remote branch

sites here; the other is internet link with internet-boundoption which is used only for internet

edge load balance.

internet-bound external interface is enabled on Hub site only for internet edge deployment,

and cannot be discovered by any branch site.

bandwidth 100000indicates thebandwidth capacity on the tunnel interface, and this BW

exported to Hub MC each 30 seconds, and used for bandwidth control and optimization. Bydefault, it is 100kbps, and should be configured based on the bandwidth provided by Service

Provider.

ip mtu 1400 andip tcp mss 1360 are suggested MTU settings to avoid fragmentation,

please refer to latest IWAN technology design and deployment guide.

BR2 example configuration:


!domai n one

vrf def aul tbordersour ce- i nter f ace Loopback0mast er 10. 8. 3. 3

!!i nter f ace Tunnel 200bandwi dt h 50000i p addr ess 10. 0. 200. 85 255. 255. 255. 0no i p redi r ectsi p mt u 1400i p nhr p aut hent i cat i on ci scoi p nhr p map mul t i cast dynami ci p nhr p net work- i d 2i p nhr p hol dt i me 600i p t cp adj ust - mss 1360

l oad- i nt er val 30del ay 1000t unnel sour ce Gi gabi t Et hernet 4t unnel mode gr e mul t i poi ntt unnel key 200tunnel vrf INET2t unnel pr otect i on i psec pr of i l e DMVPN- PROFI LE2domai n one pat h I NET

!


8/113

8

Notes:

For enterprise links over Internet ISP, we suggest to enable front VRF on the tunnel interface for

security, please refer to latest IWAN technology design and deployment guide.

This is a one-time configuration. Once done, all changes will be centralized on the Hub MC.

3.4 Branch Routers

The Branch Master Controller is the master controller at a branch site. There is no policy configuration

on this device. It receives policy from the Hub MC. This device acts as master controller for that site for

making optimization decision. The path names for external WAN interface on the branch-border router

gets discovered automatically.

Example configuration for single CPE branch (R10), similar config on branch R11:

!i nter f ace Loopback0i p address 10. 2. 10. 10 255. 255. 255. 255

!domai n onevrf def aul tbordersour ce- i nter f ace Loopback0master l ocal

mast er branchsour ce- i nter f ace Loopback0hub 10. 8. 3. 3

!i nter f ace Tunnel 100bandwi dt h 100000

i p addr ess 10. 0. 100. 10 255. 255. 255. 0no i p redi r ectsi p mt u 1400i p nhr p aut hent i cat i on ci scoi p nhrp map 10. 0. 100. 84 172. 16. 84. 4i p nhr p map mul t i cast 172. 16. 84. 4i p nhr p net work- i d 1i p nhr p hol dt i me 600i p nhrp nhs 10. 0. 100. 84i p nhr p regi st r at i on ti meout 60i p t cp adj ust - mss 1360l oad- i nt er val 30del ay 1000t unnel sour ce Gi gabi t Et hernet 2t unnel mode gr e mul t i poi ntt unnel key 100

t unnel pr otect i on i psec pr of i l e DMVPN- PROFI LE1!i nter f ace Tunnel 200bandwi dt h 50000i p addr ess 10. 0. 200. 10 255. 255. 255. 0no i p redi r ectsi p mt u 1400i p nhr p aut hent i cat i on ci scoi p nhrp map 10. 0. 200. 85 172. 16. 85. 5


9/113

9

i p nhr p map mul t i cast 172. 16. 85. 5i p nhr p net work- i d 2i p nhr p hol dt i me 600i p nhrp nhs 10. 0. 200. 85i p nhr p regi st r at i on ti meout 60i p t cp adj ust - mss 1360l oad- i nt er val 30del ay 1000

t unnel sour ce Gi gabi t Et hernet 3t unnel mode gr e mul t i poi ntt unnel key 200t unnel vrf I NET2t unnel pr otect i on i psec pr of i l e DMVPN- PROFI LE2

!

Notes:

On branch MC/BR, the MC and BR is co-located on the same router, branch MC peer and get

connected with hub MC to receive updates for policy and services.

There is no explicit configured domain name CLI on the WAN interface as hub BR, they are

discovered automatically and reported to local branch master controller.

Example configuration for dual CPE branch (R12/R13):

R12 Configuration (Branch MC and BR) includes the IP address of the Hub MC (MC1)


!domai n onevrf def aul tbordersour ce- i nter f ace Loopback0master l ocal

mast er branchsour ce- i nter f ace Loopback0hub 10. 8. 3. 3

!i nter f ace Tunnel 100bandwi dt h 100000i p addr ess 10. 0. 100. 12 255. 255. 255. 0no i p redi r ectsi p mt u 1400i p nhr p aut hent i cat i on ci scoi p nhrp map 10. 0. 100. 84 172. 16. 84. 4i p nhr p map mul t i cast 172. 16. 84. 4i p nhr p net work- i d 1i p nhr p hol dt i me 600i p nhrp nhs 10. 0. 100. 84i p nhr p regi st r at i on ti meout 60i p t cp adj ust - mss 1360l oad- i nt er val 30del ay 1000t unnel sour ce Gi gabi t Et hernet 3t unnel mode gr e mul t i poi ntt unnel key 100t unnel pr otect i on i psec pr of i l e DMVPN- PROFI LE1

!


10/113

10

R13 Configuration (BR) includes the IP address of the local MC R12


!domai n one

vrf def aul tbordersour ce- i nter f ace Loopback0mast er 10. 2. 12. 12

!i nter f ace Tunnel 200bandwi dt h 50000i p addr ess 10. 0. 200. 13 255. 255. 255. 0no i p redi r ectsi p mt u 1400i p nhr p aut hent i cat i on ci scoi p nhrp map 10. 0. 200. 85 172. 16. 85. 5i p nhr p map mul t i cast 172. 16. 85. 5i p nhr p net work- i d 2i p nhr p hol dt i me 600i p nhrp nhs 10. 0. 200. 85

i p nhr p regi st r at i on ti meout 60i p t cp adj ust - mss 1360l oad- i nt er val 30del ay 1000t unnel sour ce Gi gabi t Et hernet 6t unnel mode gr e mul t i poi ntt unnel key 200t unnel vrf I NET2t unnel pr otect i on i psec pr of i l e DMVPN- PROFI LE2

!

Notes:

For medium or large branch site, dual border routers get deployed like above configuration, R12

is a co-located MC/BR peering with hub MC, and R13 is a separate BR with front VRF design over

internet Service provider.


11/113

11

4

Defining Domain Policies

Domain policies are only defined on the Hub Master Controller and then sent over the peering

infrastructure to all MC peers. Policies can be defined per application or per DSCP. You cannot mix and

match DSCP and application-based policies in the same class group. Traffic that doesn't match any of theclassification and match statements falls into a default class which is load-balanced (no performance

measurements done).

You can either select an existing template as domain type for policy or a customized one. The available

templates for domain-policy types are listed below:

Pre-defined Template Threshold Definition

Voice

priority 1 one-way-delay threshold 150 threshold 150 (msec)

priority 2 packet-loss-rate threshold 1 (%)

priority 2 byte-loss-rate threshold 1 (%)priority 3 jitter 30 (msec)

Real-time-video


priority 1 byte-loss-rate threshold 1 (%)

priority 2 one-way-delay threshold 150 (msec)

priority 3 jitter 20 (msec)

Low-latency-data




Bulk-data




Best-effort




Scavenger




custom Defines customized user-defined policy values

Enterprise Domain policies are configured on the Hub MC (MC1):

!domai n onevrf def aul tmast er hubmoni t or - i nt er val 2 dscp ef


12/113

12

l oad- bal ancecl ass VOI CE sequence 10match dscp ef pol i cy voi cepath- pr ef erence MPLS f al l back I NET

cl ass VI DEO sequence 20match dscp af 41 pol i cy r eal - t i me-vi deomatch dscp cs4 pol i cy r eal - t i me- vi deopath- pr ef erence I NET f al l back MPLS

cl ass CRI TI CAL sequence 30mat ch dscp af 31 pol i cy cust om

pr i or i t y 2 l oss t hr eshol d 10pr i ori t y 1 one- way- del ay t hr eshol d 600

path- pr ef erence MPLS f al l back I NET!

Notes:

Configures policy on per DSCP basis only - The assumption is that DSCP marking is done on

ingress (LAN interface of the BRs) or even within the site (access switch).

Path preference for MPLS for all voice/video and critical applications.

Predefined or custom policies can be used.

Monitor interval is set to 2 second for critical applications. Default is 30 seconds. You can lowerthe monitor interval for a couple of critical applications in order to achieve a fast failover to the

secondary path. This is called quick monitor.

Load balancing is enabled for default class traffic. When load balancing is enabled, PfR adds a

default class for match all DSCP (lowest priority compared to all the other classes) and

influences this traffic. When load balancing is disabled, PfR deletes this default class and as a

part of that frees up the TCs that was learnt as a part of LB they follow the routing table.

You can check the detail policy by using the show domain master policy command

HubMC#show domai n one mast er pol i cyNo Pol i cy publ i sh pendi ng

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

cl ass VOI CE sequence 10path- pr ef erence MPLS f al l back I NETcl ass t ype: Dscp Based

match dscp ef pol i cy cust om pr i or i t y 2 packet - l oss- r at e t hr eshol d 5. 0 per cent

pr i ori t y 1 one- way- del ay t hreshol d 150 msecpr i ori t y 2 byt e- l oss- r at e threshol d 5. 0 per centNumber of Tr af f i c cl asses usi ng t hi s pol i cy: 1

cl ass VI DEO sequence 20path- pr ef erence I NET f al l back MPLScl ass t ype: Dscp Based

match dscp af 41 pol i cy cust om pr i or i t y 2 packet - l oss- r at e t hr eshol d 5. 0 per cent


match dscp cs4 pol i cy cust om pr i or i t y 2 packet - l oss- r at e t hr eshol d 5. 0 per cent

pr i ori t y 1 one- way- del ay t hreshol d 150 msecpr i ori t y 2 byt e- l oss- r at e threshol d 5. 0 per cent


13/113

13

Number of Tr af f i c cl asses usi ng t hi s pol i cy: 1

cl ass CRI TI CAL sequence 30path- pr ef erence MPLS f al l back I NETcl ass t ype: Dscp Based


pr i ori t y 1 one- way- del ay t hreshol d 600 msec

pr i or i t y 2 byte- l oss- r at e t hr eshol d 10. 0 per centNumber of Tr af f i c cl asses usi ng t hi s pol i cy: 1

cl ass def aul tmatch dscp al l

Number of Tr af f i c cl asses usi ng t hi s pol i cy: 3- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -HubMC#

Notes:

Check whether policy publish pending to remote sites.

Check detailed policy threshold per class, based on DSCP or application.

Class default is enabled when load-balance configured, and match any traffic-classes there is no

performance policy enabled.

5 Checking Domain Discovery

5.1

Check Hub MC status

HubMC#show domai n one mast er st at us

** * Domai n MC Stat us ***

Mast er VRF: Gl obal

I nst ance Type: HubI nst ance i d: 0Operat i onal st atus: UpConf i gured st atus: UpLoopback I P Addr ess: 10. 8. 3. 3Load Bal anci ng:Admi n St atus: Enabl edOperat i onal St at us: UpEnt er pr i se t op l evel pr ef i xes conf i gur ed: 1Max Cal cul at ed Ut i l i zat i on Var i ance: 1%

Last l oad bal ance at t empt : 00: 27: 23 agoLast Reason: Vari ance l ess t han 20%

Tot al unbal anced bandwi dth:External l i nks: 0 Kbps I nt er net l i nks: 0 Kpbs

Rout e Cont r ol : Enabl ed

Mi t i gat i on mode Aggr essi ve: Di sabl edPol i cy threshol d var i ance: 20Mi ni mum Mask Length: 28Sampl i ng: of f

Border s:I P addr ess: 10. 8. 2. 2Connect i on st at us: CONNECTED ( Last Updat ed 1d11h ago )I nt er f aces conf i gured:


14/113

14

Name: Tunnel 200 | t ype: ext ernal | Servi ce Pr ovi der: I NET | St atus: UPNumber of def aul t Channel s: 3

Tunnel i f : Tunnel 0

I P addr ess: 10. 8. 1. 1Connect i on st at us: CONNECTED ( Last Updat ed 1d11h ago )I nt er f aces conf i gured:

Name: Tunnel 100 | t ype: ext ernal | Servi ce Provi der: MPLS | St atus: UPNumber of def aul t Channel s: 3


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -HubMC#

Notes:

Check Operational status is up

Check Configured status is up

Check external interfaces are correctly defined with appropriate Path names

Check load-balancing is in the correct state

Two kinds of interfaces for bandwidth balance: Enterprise External links and Internet links

Disabled MC will uncontrol default class Traffic Classes

Enabled MC will control and load-share default-class Traffic Classes among all external

interfaces

Number of default Channels that can be counted for load-share between external interfaces

HubMC#show domai n one mast er exi t s

BR addr ess: 10. 8. 2. 2 | Name: Tunnel 200 | t ype: ext ernal | Pat h: I NET |Egr ess capaci t y: 50000 Kbps | Egr ess BW: 17514 Kbps | I deal : 17948 Kbps | under :

434 Kbps | Egr ess Ut i l i zat i on: 35 % DSCP: cs4[ 32] - Number of Traf f i c Cl asses[ 1]DSCP: af 41[ 34] - Number of Traf f i c Cl asses[ 1]DSCP: cs5[ 40] - Number of Traf f i c Cl asses[ 1]

BR addr ess: 10. 8. 1. 1 | Name: Tunnel 100 | t ype: ext ernal | Pat h: MPLS |Egr ess capaci t y: 100000 Kbps | Egr ess BW: 36331 Kbps | I deal : 35896 Kbps | over :

435 Kbps | Egr ess Ut i l i zat i on: 36 % DSCP: cs1[ 8] - Number of Traf f i c Cl asses[ 1]

DSCP: af 11[ 10] - Number of Traf f i c Cl asses[ 1]DSCP: af 31[ 26] - Number of Traf f i c Cl asses[ 1]DSCP: ef [ 46] - Number of Traf f i c Cl asses[ 1]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -HubMC#

Notes:

Check external interfaces capacity and egress utilization

Check number of Traffic Classes per DSCP on external interface

Check the range of egress utilization


15/113

15

HubMC#show domai n one mast er peer i ngPeer i ng st ate: Enabl edOr i gi n: Loopback0( 10. 8. 3. 3)Peer i ng t ype: Li st enerSubscr i bed servi ce:

cent - pol i cy ( 2) :s i te- pref i x (1) :

Last Not i f i cat i on I nf o: 00: 23: 15 ago, Si ze: 160, Compr essed si ze: 144, St at us:

No Er r or, Count : 3servi ce- provi der ( 4) :gl obal s (5) :

Last Not i f i cat i on I nf o: 00: 03: 09 ago, Si ze: 325, Compr essed si ze: 218, St at us:No Er r or, Count : 6

pmi ( 3) :

Publ i shed ser vi ce:s i te- pref i x (1) :

Last Publ i sh I nf o: 00: 03: 10 ago, Si ze: 209, Compr essed si ze: 138, St at us: NoError

cent - pol i cy ( 2) :Last Publ i sh I nf o: 00: 02: 58 ago, Si ze: 2244, Compr essed si ze: 468, St atus: No

Errorpmi ( 3) :

Last Publ i sh I nf o: 02: 03: 12 ago, Si ze: 2088, Compr essed si ze: 458, St atus: No

Errorgl obal s (5) :Last Publ i sh I nf o: 00: 03: 09 ago, Si ze: 325, Compr essed si ze: 198, St at us: No

ErrorHubMC#HubMC#

Notes:

Check master peering status

site-prefix, cent-policy, pmi, and globals service Publish and Subscription status

All of the services are automatically generated by Hub MC, then published by EGIRP SAF

framework

Hub MC publish all of four type of services, and subscribe site-prefix and globals service from

remote branch sites at the same time

5.2 Check Hub BR Status

HubBR1#show domai n one bor der st at us

Thu Oct 30 05: 25: 00. 876- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

**** Bor der St atus****

I nst ance St atus: UP

Present st atus l ast updated: 02: 07: 43 agoLoopback: Conf i gur ed Loopback0 UP ( 10. 8. 2. 2)Mast er : 10. 8. 3. 3Connect i on St atus wi t h Mast er: UPMC connect i on i nf o: CONNECTI ON SUCCESSFULConnect ed f or: 02: 07: 42Rout e- Cont r ol : Enabl edMi ni mumMask l ength: 28Sampl i ng: of f


16/113

16

Mi ni mum Requi r ement : MetExter nal Wan i nt erf aces:

Name: Tunnel 100 I nter f ace I ndex: 14 SNMP I ndex: 9 SP: MPLS Stat us: UP

Aut o Tunnel i nf ormati on:

Name: Tunnel 0 i f _i ndex: 15Bor der s r eachabl e vi a t hi s t unnel : 10. 8. 2. 2,

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -HubBR1#

Notes:

Check external interfaces are correctly defined

Check that connection status with MC is up

Check that remote BR is discovered

Check that Minimum requirement met

PFR auto-tunnel interface is created automatically to all other border routers in the same site

HubBR1#show domai n one bor der peer i ngPeer i ng st ate: Enabl edOr i gi n: Loopback0( 10. 8. 2. 2)Peer i ng t ype: Peer( Wi t h 10. 8. 3. 3)Subscr i bed servi ce:

pmi ( 3) :Last Noti f i cat i on I nf o: 02: 09: 49 ago, Si ze: 2088, Compr essed si ze: 478, St atus:

No Er r or, Count : 1s i te- pref i x (1) :


gl obal s (5) :Last Not i f i cat i on I nf o: 00: 09: 48 ago, Si ze: 325, Compr essed si ze: 218, St at us:

No Er r or, Count : 9

Publ i shed ser vi ce:

HubBR1#

Notes:

Check border router peering status

Border router subscribe pmi, site-prefix and globals service;

To check the CENT border status on ASR1000 platform, we need IOS-XE platform specific show

command:

HubBR2#show pl at f orm sof t ware pf r v3 r p act i ve smar t - probeCENT smar t probe paramet er s :

Tot al number of CENT smar t probe: 1

Par ameters :vrf i d = 0


17/113

17

Probe sr c = 10. 8. 3. 3Src por t = 18000, Dst por t = 19000Unreach t i me = 1000, Pr obe per i od = 500Di scovery = f al seDscp bi t map = 0xf f f f f f f f f f f f f f f fi nterval = 10000Di scovery_pr obe = t r uemi ni mumpref i x l ength = 28

HubBR2#show pl at f orm sof t ware pf r v3 f p act i ve smar t - probeCENT smar t probe paramet er s :

Tot al number of CENT smar t probe: 1

Par ameters :vrf i d = 0Probe sr c = 10. 8. 3. 3Src por t = 18000, Dst por t = 19000Unreach t i me = 1000, Pr obe per i od = 500Di scovery = f al seDscp bi t map = 0xf f f f f f f f f f f f f f f fi nterval = 10000Di scovery_pr obe = t r ue

mi ni mumpref i x l ength = 28

HubBR2#show pl atf or m har dware qf p act i ve f eat ur e pf r v3 cl i ent gl obal pf r v3- i nst ancedetai lCENT QFP CLI ENT GLOBAL I NFO

Number of I nst ances: 1

I nst ancehash val : 5tbl i d: 0symmet r y: Of fdi scover y: Of fdi scovery_pr obe: Onpr obe i nf o:

pr obe sr c: 10. 8. 3. 3, sr c port : 18000, dst port : 19000unr each t i me: 1000, probe per i od: 500dscp bi t map: 0xf f f f f f f f f f f f f f f f , i nt erval : 10000mml : 28

exmemi nf o:PPE addr: 0xe80b7830

Notes:

Check PfR border router instance in data-plane;

Check PfR border instance and smart-probe related parameter: unreachable and probe timer

and minimum prefix length, etc;

Check the fast-monitor DSCP bitmap which DSCP get enabled for fast borrowout


18/113

18

5.3

Check Hub Discovered sites

All sites that belong to the Domain should appear. This shows that SAF peering is correctly set up. In this

workflow, we have two remote sites Branch10, Branch 11 and local hub sites connected:

HubMC#show der i ved- conf i g | sect i on ei grp

r out er ei gr p #AUTOCFG# ( API - generat ed aut o- conf i gurat i on, not user conf i gurabl e)!servi ce- f ami l y i pv4 aut onomous- syst em59501!sf - i nt erf ace Loopback0hel l o- i nt er val 120hol d- t i me 600

exi t - s f - i nter f ace!t opol ogy baseexi t - sf - t opol ogyr emote- nei ghbors sour ce Loopback0 uni cast - l i st en

exi t - servi ce- f ami l y

HubMC#show ei grp ser vi ce- f ami l y i pv4 nei ghbor sEI GRP- SFv4 VR( #AUTOCFG#) Ser vi ce- Fami l y Nei ghbor s f or AS(59501)

H Addr ess I nt er f ace Hol d Upt i me SRTT RTO Q Seq( sec) ( ms) Cnt Num

2 10. 2. 10. 10 Lo0 595 01: 59: 20 5 100 0 111 10. 2. 11. 11 Lo0 549 02: 08: 36 1 100 0 163 10. 8. 1. 1 Lo0 498 02: 12: 11 1 100 0 40 10. 8. 2. 2 Lo0 526 02: 12: 42 1 100 0 7HubBR1#

Notes:

Check eigrp SAF configuration automatically enabled;

Check EIGRP SAF peering status between local and remote sites;

HubMC#show domai n one mast er di scovered- si t es

** * Domai n MC DI SCOVERED si t es ***

Number of si t es: 3*Traf f i c cl asses [ Per f ormance based] [ Load- bal ance based]

Si t e I D: 255. 255. 255. 255DSCP : def aul t [ 0] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : af 31[ 26] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : cs4[ 32] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : af 41[ 34] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : cs5[ 40] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : ef [ 46] - Number of t r af f i c cl asses[ 0] [ 0]

Si t e I D: 10. 2. 10. 10

DSCP : def aul t [ 0] - Number of t r af f i c cl asses[ 1] [ 1]DSCP : af 31[ 26] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : cs4[ 32] - Number of t r af f i c cl asses[ 1] [ 0]DSCP : af 41[ 34] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : cs5[ 40] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : ef [ 46] - Number of t r af f i c cl asses[ 1] [ 0]

Si t e I D: 10. 2. 11. 11DSCP : def aul t [ 0] - Number of t r af f i c cl asses[ 0] [ 0]


19/113

19

DSCP : af 31[ 26] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : cs4[ 32] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : af 41[ 34] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : cs5[ 40] - Number of t r af f i c cl asses[ 0] [ 0]DSCP : ef [ 46] - Number of t r af f i c cl asses[ 0] [ 0]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -HubMC#

At this point the Hub BRs can generate Discovery Probes (Smart Probes) to all remote sites to help them

discover their external interfaces and their path names.

5.4 Check Branch MC Status

Br anch10#show domai n one mast er st at us

** * Domai n MC Stat us ***

Mast er VRF: Gl obal

I nst ance Type: Br anchI nst ance i d: 0Oper at i onal st at us: UpConf i gur ed st at us: UpLoopback I P Addr ess: 10. 2. 10. 10Load Bal anci ng:Operat i onal St at us: UpMax Cal cul at ed Ut i l i zat i on Var i ance: 21%

Last l oad bal ance at t empt : 00: 00: 07 agoLast Reason: No channel s yet f or l oad bal anci ngTot al unbal anced bandwi dth:

External l i nks: 5327 Kbps I nt er net l i nks: 0 KpbsRout e Cont r ol : Enabl edMi t i gat i on mode Aggr essi ve: Di sabl edPol i cy threshol d var i ance: 20

Mi ni mum Mask Length: 28Sampl i ng: of fMi ni mum Requi r ement : Met

Border s:I P addr ess: 10. 2. 10. 10Connect i on st at us: CONNECTED ( Last Updat ed 02: 03: 22 ago )I nt er f aces conf i gured:

Name: Tunnel 100 | t ype: ext ernal | Servi ce Provi der: MPLS | St atus: UPNumber of def aul t Channel s: 0

Name: Tunnel 200 | t ype: ext ernal | Servi ce Pr ovi der: I NET | St atus: UPNumber of def aul t Channel s: 0


- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Branch10#

Notes:


20/113

20

Check that external interfaces are listed with their correct path names. That means smart

probes are correctly received and decoded by local BRs. If external interfaces are not correctly

discovered, that means smart probes are not correctly received:

Check that remote MC address is reachable over all external interfaces

Check that Smart Probes are correctly received

Check path names are correct. If path names are not listed check that smart probes are received

from the hub. Branch MC loopback address has to be announced and routable from the hub

Border Routers.

To check the smart probes packets (SMP)are correctly received on each external interface, one can

define an access-list to match SMP packets:

access-list 100 permit udp any eq 18000 any eq 19000

show ip access-listto check whether the counter keeps increasing, you could also use conditional

debugor embedded packet capture(EPC) to capture the smart-probe packets on the external interface

either on source or destination border router, please refer to section7.4 Embedded Packet Capture

(EPC).

Check Policy is received from the hub MC: show domain master policy

Br anch10#show domai n one mast er pol i cy- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

cl ass VOI CE sequence 10path- pr ef erence MPLS f al l back I NETcl ass t ype: Dscp Based

match dscp ef pol i cy cust om pr i or i t y 2 packet - l oss- r at e t hr eshol d 5. 0 per cent


Number of Tr af f i c cl asses usi ng t hi s pol i cy: 1

cl ass VI DEO sequence 20path- pr ef erence I NET f al l back MPLScl ass t ype: Dscp Based



match dscp cs4 pol i cy cust om pr i or i t y 2 packet - l oss- r at e t hr eshol d 5. 0 per cent


cl ass CRI TI CAL sequence 30

path- pr ef erence MPLS f al l back I NETcl ass t ype: Dscp Basedmatch dscp af 31 pol i cy cust om

pr i or i t y 2 packet - l oss- r at e t hr eshol d 10. 0 per centpr i ori t y 1 one- way- del ay t hreshol d 600 msecpr i or i t y 2 byte- l oss- r at e t hr eshol d 10. 0 per cent

cl ass def aul tmatch dscp al l


21/113

21

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Branch10#

5.5 Check Branch BR Status

Br anch10#show domai n one border st at us

Thu Oct 30 05: 42: 00. 647- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

**** Bor der St atus****

I nst ance St atus: UPPresent st atus l ast updated: 02: 11: 47 agoLoopback: Conf i gur ed Loopback0 UP ( 10. 2. 10. 10)Master : 10. 2. 10. 10Connect i on St atus wi t h Mast er: UPMC connect i on i nf o: CONNECTI ON SUCCESSFUL

Connect ed f or: 02: 11: 41Rout e- Cont r ol : Enabl edMi ni mumMask l ength: 28Sampl i ng: of fMi ni mum Requi r ement : MetExter nal Wan i nt erf aces:

Name: Tunnel 100 I nter f ace I ndex: 14 SNMP I ndex: 9 SP: MPLS Stat us: UPName: Tunnel 200 I nter f ace I ndex: 15 SNMP I ndex: 10 SP: I NET Stat us: UP

Aut o Tunnel i nf ormati on:

Name: Tunnel 0 i f _i ndex: 19Bor der s r eachabl e vi a t hi s t unnel :

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Branch10#

Step 1.Check that external interfaces are listed with their correct path names. That means smart probes

are correctly received and decoded by local BRs.

Step 2.Check path names are correct. If path names are not listed check that smart probes are received

from the hub. Branch MC loopback address has to be announced and routable from the hub Border

Routers.

Step 3.Check that Minimum requirement met.

If the minimum requirement is not MET, check the SAF peering on the local master it should correctly

peer with the hub MC:

Br anch10#show ei gr p servi ce- f ami l y i pv4 nei ghbors det ai lEI GRP- SFv4 VR( #AUTOCFG#) Ser vi ce- Fami l y Nei ghbor s f or AS(59501)H Addr ess I nt er f ace Hol d Upt i me SRTT RTO Q Seq

( sec) ( ms) Cnt Num0 10. 8. 3. 3 Lo0 497 02: 12: 18 5 100 0 31

Remote St at i c nei ghbor ( st ati c mul t i hop)Ver si on 17. 0/ 4. 0, Ret r ans: 0, Ret ri es: 0, Pref i xes: 6


22/113

22

Topol ogy- i ds f r om peer - 0Max Nbrs : 65535, Curr ent Nbrs : 0R10#

Check PfRv3 peering on the local master: show domain master peering

Branch10#show domai n one mast er peer i ng

Peer i ng st ate: Enabl edOr i gi n: Loopback0( 10. 2. 10. 10)Peer i ng t ype: Li st ener , Peer ( Wi t h 10. 8. 3. 3)Subscr i bed servi ce:

cent - pol i cy ( 2) :Last Noti f i cat i on I nf o: 00: 24: 15 ago, Si ze: 2244, Compr essed si ze: 488, St atus:

No Er r or, Count : 5s i te- pref i x (1) :


servi ce- provi der ( 4) :gl obal s (5) :


Publ i shed ser vi ce:

s i te- pref i x (1) :Last Publ i sh I nf o: 00: 49: 11 ago, Si ze: 160, Compr essed si ze: 124, St at us: No

Errorgl obal s (5) :

Last Publ i sh I nf o: 10: 29: 09 ago, Si ze: 325, Compr essed si ze: 198, St at us: NoErrorBranch10#

Domain Policies are defined on the Hub MC and sent over the SAF infrastructure to all MC peers.

Each time Domain policies are updated on the hub MC, they are refreshed and sent over to all

MC peers.

For any branch MC not receiving any update, please confirm whether MTU settings are

consistently across the path which might lead to any EIGRP SAF packets get dropped

unexpectedly.

Step 4.Check Monitor specification is received from the hub MC -> show domain one border pmi

Step 5.Check that performance monitors are correctly applied on the external interfaces, on ingress and

egress:

Branch10#show domai n one bor der pmi

**** CENT PMI I NFORMATI ON****

I ngr ess pol i cy CENT- Pol i cy- I ngr ess- 0- 4:I ngr ess pol i cy act i vat ed on:Tunnel 200 Tunnel 100

[ SNI P]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


23/113

23

Egr ess pol i cy CENT- Pol i cy- Egr ess- 0- 3:Egr ess pol i cy act i vat ed on:

Tunnel200 Tunnel100- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -PMI [ Egr ess- aggregat e] - FLOW MONI TOR[ MON- Egr ess- aggregat e- 0- 48- 1]

Tr i gger Nbar: No

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

PMI [ Egr ess- pr ef i x- l ear n] - FLOW MONI TOR[ MON- Egr ess- pr ef i x- l ear n- 0- 48- 2]

Wi t h appl i cat i on based pol i cy:

Branch10#show domai n one bor der pmi


I ngr ess pol i cy CENT- Pol i cy- I ngr ess- 0- 4:I ngr ess pol i cy act i vat ed on:

Tunnel 200 Tunnel 100

[ SNI P]

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Egr ess pol i cy CENT- Pol i cy- Egr ess- 0- 3:Egr ess pol i cy act i vat ed on:

Tunnel200 Tunnel0 Tunnel100- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -PMI [ Egr ess- aggregat e] - FLOW MONI TOR[ MON- Egr ess- aggregat e- 0- 48- 1]

Tr i gger Nbar: Yes

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -PMI [ Egr ess- pr ef i x- l ear n] - FLOW MONI TOR[ MON- Egr ess- pr ef i x- l ear n- 0- 48- 2]

Notes:

PMI stands for Performance Monitoring Instances;

Performance monitor definitions are received from the Hub MC;

Policy are activated on all external interfaces on border router;

Auto-Tunnel and NBAR get activated dynamically with application based policy only.

5.6

Check Unified Performance Monitor

PfR version 3 leverages AVC/MMA infrastructure for passive performance monitoring, includes site-

prefix and traffic-class learning on WAN interface egress direction, and per DSCP performancemonitoring on ingress direction. These three flow monitor are generated automatically:

Br anch10#show flow monitor type performance-monitorFl ow Moni t or t ype per f ormance- moni t orMON-Egress-aggregate-0-48-9:

Descri pt i on : User def i nedFl ow Record : CENT- FLOWREC- Egr ess- aggregat e- 0- 11


24/113

24

Fl ow Expor t er : CENT_FLOW_EXP- 2Cache t ype : synchr oni zed

ent r i es : 4000i nt er val : 30 ( seconds)hi story s i ze : 0 ( i nt erval s)t i meout : 1 ( i nt erval s)export spreadi ng: TRUE

I nt er f ace appl i ed : 2

Fl ow Moni t or t ype per f ormance- moni t orMON-Egress-prefix-learn-0-48-10:Descri pt i on : User def i nedFl ow Recor d : CENT- FLOWREC- Egr ess- pr ef i x- l ear n- 0- 12Fl ow Expor t er : CENT_FLOW_EXP- 2Cache t ype : synchr oni zed

ent r i es : 700i nt er val : 30 ( seconds)hi story s i ze : 0 ( i nt erval s)t i meout : 1 ( i nt erval s)export spr eadi ng: FALSE


Fl ow Moni t or t ype per f ormance- moni t orMON-Ingress-per-DSCP-0-48-11:Descri pt i on : User def i nedFl ow Record : CENT- FLOWREC- I ngr ess- per - DSCP- 0- 13

Fl ow Export er : not conf i gur edCache t ype : synchr oni zedent r i es : 2000i nt er val : 30 ( seconds)hi story s i ze : 0 ( i nt erval s)t i meout : 1 ( i nt erval s)export spr eadi ng: FALSE


Notes:

performance monitor cache size setting based on platform capability;

export spreading enabled for egress monitor to avoid export storm under scale condition; performance monitor with a 30 sec interval by default;

You should be able to review the detail performance monitor flow definition, which is generated

automatically when PfR gets configured: show performance monitor internal flow-def-master

Br anch10#show performance monitor internal flow-def-masterFNF Moni t or : MON- I ngr ess- per - DSCP- 0-48- 11 Name :MMA_DB_c_ f def _1340502592_12

User s : 0Key Fi el ds:Non Key Fi el ds:

Name: t r ansport packets expect ed counterName: t r anspor t packets l ost count erName: t r ansport packet s l ost r ateName: t r ansport byt es expect edName: t r anspor t bytes l ostName: t r ansport bytes l ost r at eName: pf r one- way- del ay sampl esName: pf r one- way- del ay sum


25/113

25

Name: pf r one- way- del ayName: networ k del ay sampl eName: networ k del ay sum

Name: networ k del ay averageName: t r ansport r t p j i t t er i nt er ar r i val sampl esName: t r ansport r t p j i t t er i nt er arr i val sum

Name: t r anspor t r t p j i t t er i nt er ar r i val meanName: count er bytes l ong

Name: count er packet s l ongName: t i mest amp absol ute moni t ori ng- i nt erval st artName: t i mest amp i nterval

Name : MMA_DB_m_f def _1340502592_12User s : 0Key Fi el ds:

Name: pf r si t e sour ce i d i pv4Name: pf r si t e dest i nat i on i d i pv4Name: i p dscpName: i nter f ace i nputName: pol i cy perf ormance- moni t or cl assi f i cat i on hi erarchy

Non Key Fi el ds:Name: vm ( 72 / 0x48)

Name : MMA_DB_t _f def _1340502592_12User s : 0Key Fi el ds:

Name: t i mest amp absol ute moni t or i ng- i nterval endName: pf r si t e sour ce i d i pv4Name: pf r si t e dest i nat i on i d i pv4Name: i p dscpName: i nter f ace i nputName: pol i cy perf ormance- moni t or cl assi f i cat i on hi erarchy

Non Key Fi el ds:Name: t r ansport packets expect ed counterName: t r anspor t packets l ost count erName: t r ansport byt es expect edName: t r anspor t bytes l ostName: pf r one- way- del ay sampl esName: pf r one- way- del ay sum

Name: networ k del ay sampl eName: networ k del ay sum

Name: tr ansport rt p j i t t er i nt er ar r i val sampl es

Name: t r ansport r t p j i t t er i nt er arr i val sum Name: count er bytes l ongName: count er packet s l ongName: t i mest amp absol ute moni t ori ng- i nt erval st artName: t i mest amp i ntervalName: vm ( 8 / 0x8)

FNF Moni t or : MON- Egr ess- aggregat e- 0- 48- 9 Name :MMA_DB_c_ f def _2307076292_10


Name: t i mest amp absol ute moni t ori ng- i nt erval st artName: count er bytes l ongName: count er packet s l ongName: i p pr otocol

Name: pf r si t e dest i nat i on i d i pv4Name: pf r si t e sour ce i d i pv4Name: t i mest amp i nterval


Name: i pv4 desti nati on pr ef i xName: i pv4 dest i nat i on maskName: pf r si t e dest i nat i on pr ef i x i pv4


26/113

26

Name: pf r si t e desti nati on pr ef i x mask i pv4Name: i p dscpName: i nter f ace out put

Non Key Fi el ds:Name: vm ( 72 / 0x48)

Name : MMA_DB_t _f def _2307076292_10User s : 0Key Fi el ds:

Name: t i mest amp absol ute moni t or i ng- i nterval endName: i pv4 desti nati on pr ef i xName: i pv4 dest i nat i on maskName: pf r si t e dest i nat i on pr ef i x i pv4Name: pf r si t e desti nati on pr ef i x mask i pv4Name: i p dscpName: i nter f ace out put

Non Key Fi el ds:Name: t i mest amp absol ute moni t ori ng- i nt erval st artName: count er bytes l ongName: count er packet s l ongName: i p pr otocolName: pf r si t e dest i nat i on i d i pv4Name: pf r si t e sour ce i d i pv4Name: t i mest amp i ntervalName: vm ( 8 / 0x8)

FNF Moni t or : MON- Egr ess- pr ef i x- l ear n- 0- 48- 10 Name :MMA_DB_c_ f def _2587394358_11


Name: count er bytes l ongName: count er packet s l ongName: t i mest amp absol ute moni t ori ng- i nt erval st artName: t i mest amp i nterval


Name: i pv4 source pr ef i xName: i pv4 source maskName: r out i ng vr f i nput

Non Key Fi el ds:Name: vm ( 72 / 0x48)Name : MMA_DB_t _f def _2587394358_11User s : 0Key Fi el ds:

Name: t i mest amp absol ute moni t or i ng- i nterval endName: i pv4 source pr ef i xName: i pv4 source maskName: r out i ng vr f i nput

Non Key Fi el ds:Name: count er bytes l ongName: count er packet s l ongName: t i mest amp absol ute moni t ori ng- i nt erval st artName: t i mest amp i ntervalName: vm ( 8 / 0x8)

Branch10#

Notes:


27/113

27

One ingress monitor MON-Ingress-per-DSCP-0-48-11collects performance metrics per

channel (per pair of site and DSCP value). Note the key fields: pfr site source id ipv4, pfr site

destination id ipv4, ip dscp anddomain pathused to identify a channel.

One egress performance monitor MON-Egress-aggregate-0-48-9to collect bandwidth per

Traffic Class - Note the key fields: pfr site destination prefix ipv4, mask, ip dscp, or application

IDused to identify a Traffic Class.

One egress performance monitor MON-Egress-prefix-learn-0-48-10 to catch new source

prefixes and advertise them to all peers. Again note the key fields: cef ipv4 source prefix/mask

that is used to identify new source prefixes.

Performance monitor get activated on external interface when domain path configured on hub BR or

discovered on branch BR:

Br anch10#show domain one border pmi


I ngr ess pol i cy CENT- Pol i cy- I ngr ess- 0- 9:I ngr ess pol i cy act i vat ed on:

Tunnel 200 Tunnel 100- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -PMI [ I ngr ess- per - DSCP] - FLOW MONI TOR[ MON- I ngr ess- per - DSCP- 0- 48- 11]

moni t or - i nt er val : 30key- l i s t :

pf r si t e sour ce i d i pv4pf r si t e desti nat i on i d i pv4i p dscpi nt er f ace i nputpol i cy per f or mance- moni t or cl assi f i cat i on hi er ar chy

Non- key- l i st:t r anspor t packet s l ost r at e

t ranspor t byt es l ost rat epf r one- way- del aynet work del ay aver aget ransport rt p j i t t er i nt er arr i val meancounter bytes l ongcounter packets l ongt i mestamp absol ut e moni t ori ng- i nt erval st art

DSCP- l i st:ef - [ cl ass: CENT- Cl ass- I ngr ess- DSCP- ef - 0- 22]

packet - l oss-r at e: react_i d[ 70] - pri or i t y[ 2] - t hreshol d[ 5. 0 percent ]one- way- del ay: r eact _i d[ 71] - pr i or i t y[1]- t hr eshol d[ 150 msec]net wor k- del ay- avg: r eact _i d[ 72] - pr i or i t y[ 1] - t hr eshol d[ 300 msec]byt e- l oss-r at e: react_i d[ 73] - pri or i t y[ 2] - t hreshol d[ 5. 0 percent ]

af41- [ cl ass: CENT-Cl ass- I ngr ess- DSCP- af 41- 0- 23]packet - l oss-r at e: react_i d[ 74] - pri or i t y[ 2] - t hreshol d[ 5. 0 percent ]one- way- del ay: r eact _i d[ 75] - pr i or i t y[1]- t hr eshol d[ 150 msec]

net wor k- del ay- avg: r eact _i d[ 76] - pr i or i t y[ 1] - t hr eshol d[ 300 msec]byt e- l oss-r at e: react_i d[ 77] - pri or i t y[ 2] - t hreshol d[ 5. 0 percent ]cs4- [ cl ass: CENT- Cl ass- I ngr ess- DSCP- cs4- 0- 24]

packet - l oss-r at e: react_i d[ 78] - pri or i t y[ 2] - t hreshol d[ 5. 0 percent ]one- way- del ay: r eact _i d[ 79] - pr i or i t y[1]- t hr eshol d[ 150 msec]net wor k- del ay- avg: r eact _i d[ 80] - pr i or i t y[ 1] - t hr eshol d[ 300 msec]byt e- l oss-r at e: react_i d[ 81] - pri or i t y[ 2] - t hreshol d[ 5. 0 percent ]

af31- [ cl ass: CENT-Cl ass- I ngr ess- DSCP- af 31- 0- 25]packet - l oss- r at e: r eact_i d[ 82] - pr i or i t y[ 2] - t hr eshol d[ 10. 0 per cent ]


28/113

28

one- way- del ay: r eact _i d[ 83] - pr i or i t y[1]- t hr eshol d[ 600 msec]net wor k- del ay- avg: r eact _i d[ 84] - pr i or i t y[ 1] - t hr eshol d[ 1200 msec]byt e- l oss-r at e: react_i d[ 85] - pri or i t y[ 2] - t hreshol d[ 10. 0 percent ]

Expor t er - l i st : None- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Egr ess pol i cy CENT- Pol i cy- Egr ess- 0- 8:

Egr ess pol i cy act i vat ed on:Tunnel 200 Tunnel 100

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -PMI [ Egr ess- aggregat e] - FLOW MONI TOR[ MON- Egr ess- aggregat e- 0- 48- 9]

moni t or - i nt er val : 30Tr i gger Nbar: Nomi ni mummask- l engt h: 28key- l i s t :

i pv4 dest i nat i on pr ef i xi pv4 dest i nat i on maskpf r si t e desti nat i on pref i x i pv4pf r si t e dest i nat i on pr ef i x mask i pv4i p dscpi nt er f ace out put

Non- key- l i st:t i mestamp absol ut e moni t ori ng- i nt erval st art

counter bytes l ongcounter packets l ongi p pr ot ocolpf r si t e desti nat i on i d i pv4pf r si t e sour ce i d i pv4

DSCP- l i st : N/ ACl ass: CENT- Cl ass- Egr ess- ANY- 0- 21

Expor t er - l i s t :10. 2. 10. 10

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -PMI [ Egr ess- pr ef i x- l ear n] - FLOW MONI TOR[ MON- Egr ess- pr ef i x- l ear n- 0- 48- 10]

moni t or - i nt er val : 30mi ni mummask- l engt h: 28key- l i s t :

i pv4 sour ce pr ef i x

i pv4 source maskr out i ng vr f i nputNon- key- l i st:

counter bytes l ongcounter packets l ongt i mestamp absol ut e moni t ori ng- i nt erval st art


Expor t er - l i s t :10. 2. 10. 10

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Branch10#

Notes:

PMI stands for Performance Monitoring Instances.

Performance monitor definitions are received from the Hub MC

One ingress performance monitor with 2 sec interval for all critical applications, with DSCP EF,

AF41/CS4, and AF31 - this monitor is called "quick" monitor.


29/113

29

Check service-policy stats updated correctly for each class-map on the external interfaces:

Br anch10#show domai n one bor der pmi pol i cy- map i nt er f ace t unnel 100Tunnel 100

Ser vi ce- pol i cy per f or mance- moni t or i nput : CENT- Pol i cy- I ngr ess- 0- 9

Cl ass- map: CENT- Cl ass- I ngr ess- DSCP- ef - 0- 22 ( match- any)7388086 packet s, 3506803395 byt es30 second of f ered r at e 11266000 bps, drop r at e 0000 bpsMatch: dscp ef (46)Tot al Packet s cl ass i f i ed: 0Tot al Byt es cl ass i f i ed: 0Moni t or AOR: di sabl ed

Cl ass- map: CENT- Cl ass- I ngr ess- DSCP- af 41- 0- 23 (match- any)6902212 packet s, 3274797427 byt es30 second of f ered r at e 11291000 bps, drop r at e 0000 bpsMatch: dscp af 41 ( 34)Tot al Packet s cl ass i f i ed: 0Tot al Byt es cl ass i f i ed: 0

Moni t or AOR: di sabl ed

Cl ass- map: CENT- Cl ass- I ngr ess- DSCP- cs4- 0- 24 (match- any)7642239 packet s, 3407622455 byt es30 second of f ered r at e 11368000 bps, drop r at e 0000 bpsMatch: dscp cs4 ( 32)Tot al Packet s cl ass i f i ed: 0Tot al Byt es cl ass i f i ed: 0Moni t or AOR: di sabl ed

Cl ass- map: CENT- Cl ass- I ngr ess- DSCP- af 31- 0- 25 (match- any)12345248 packet s, 5860560391 byt es30 second of f ered r at e 18787000 bps, drop r at e 0000 bpsMatch: dscp af 31 ( 26)Tot al Packet s cl ass i f i ed: 0Tot al Byt es cl ass i f i ed: 0

Moni t or AOR: di sabl ed

Cl ass- map: cl ass- def aul t ( match- any)0 packets, 0 byt es30 second of f ered r at e 0000 bps, drop rate 0000 bpsMat ch: any

Servi ce- pol i cy perf ormance- moni t or out put : CENT- Pol i cy-Egr ess- 0- 8

Cl ass- map: CENT- Cl ass- Egr ess- ANY- 0- 21 ( match- any)24999229 packet s, 3233800218 byt es30 second of f ered r at e 10759000 bps, drop r at e 0000 bpsMat ch: access - group name mma- dvmc- acl #3Tot al Packet s cl ass i f i ed: 0Tot al Byt es cl ass i f i ed: 0Moni t or AOR: di sabl ed

Cl ass- map: cl ass- def aul t ( match- any)0 packets, 0 byt es30 second of f ered r at e 0000 bps, drop rate 0000 bpsMat ch: any

Branch10#Br anch10#show i p access- l i st s dynami cExtended I P access l i st mma- dvmc- acl #3

10 deny i p any 224. 0. 0. 0 15. 255. 255. 255


30/113

30

20 deny i p any any dscp cs630 per mi t t cp any any40 permi t udp any neq 18000 any neq 1900050 per mi t i cmp any any

Notes:

Check the packets/bytes counter accounted properly;

TCP, UDP and ICMP flows are learned and supported in this phase;

Multicast and control-protocol packets with DSCP CS6 are not controlled by PfR;

Br anch10#show per f ormance moni t or cache moni t or MON- Egr ess- pref i x- l ear n- 0- 48- 10 det ai lf ormat r ecor dMoni t or: MON- Egr ess- pr ef i x- l ear n- 0- 48- 10

Dat a Col l ect i on Moni t or :

Cache t ype: Synchr oni zed ( Pl at f orm cache)Cache si ze: 700

Cur r ent ent r i es: 1Hi gh Wat er mar k: 1

Fl ows added: 103Fl ows aged: 102Synchroni zed t i meout ( secs) : 30

I PV4 SOURCE PREFI X: 10. 1. 10. 0I PV4 SOURCE MASK: / 24I P VRF I D I NPUT: 0 ( DEFAULT)counter byt es l ong: 26201651counter packets l ong: 258674t i mest amp moni t or st art : 16: 14: 30. 000

Notes:

Check site-prefix flow monitor cache records;

Prefix is learned based on IPV4 SOURCE PREFIX/MASK in CEF;

Br anch10#show performance monitor cache monitor MON-Egress-aggregate-0-48-9 detailMoni t or: MON- Egr ess- aggr egate- 0- 48- 9


Cache t ype: Synchr oni zed ( Pl at f orm cache)Cache si ze: 4000Cur r ent ent r i es: 7Hi gh Wat er mar k: 12


I PV4 DST PREFI X I PV4 DST MASK I PV4 DESTI NATI ON SI TE PREFI X I PV4 DESTI NATI ON SI TEPREFI X MASK I P DSCP I NTF OUTPUT t i me moni t or st ar t byt es l ongpkts l ong i p pr ot pf r dest i nat i on si t e i d pf r sour ce si t e i d


31/113

31

=============== ============= ============================================================= ======= ==================== ====================================== ==================== ======= =========================================10. 8. 101. 0 / 28 10. 8. 0. 0/ 16 0x28 Tu200 16: 12: 30. 000 88491879 6 10. 8. 3. 3 10. 2. 10. 1010. 8. 101. 0 / 28 10. 8. 0. 0

/ 16 0x20 Tu100 16: 12: 30. 000 465747245981 6 10. 8. 3. 3 10. 2. 10. 1010. 8. 101. 0 / 28 10. 8. 0. 0/ 16 0x22 Tu100 16: 12: 30. 000 705776069637 6 10. 8. 3. 3 10. 2. 10. 1010. 8. 101. 0 / 28 10. 8. 0. 0/ 16 0x0A Tu200 16: 12: 30. 000 2231052237 6 10. 8. 3. 3 10. 2. 10. 1010. 8. 101. 0 / 28 10. 8. 0. 0/ 16 0x08 Tu200 16: 12: 30. 000 2221422226 6 10. 8. 3. 3 10. 2. 10. 1010. 8. 101. 0 / 28 10. 8. 0. 0/ 16 0x1A Tu100 16: 12: 30. 000 11752935115975 6 10. 8. 3. 3 10. 2. 10. 1010. 8. 101. 0 / 28 10. 8. 0. 0/ 16 0x2E Tu100 16: 12: 30. 000 7044009

69518 6 10. 8. 3. 3 10. 2. 10. 10

Notes:

Check traffic-class flow monitor cache records;

Traffic-class is learned based on site-prefix database with longest match of IPV4 DESTINATION

SITE PREFIX /MASK;

Internet traffic-class learned based on IPV4 Destination PREFIX/MASK and minimum-mask-

length.

Br anch10#show performance monitor cache monitor MON-Ingress-per-DSCP-0-48-11 detailf ormat r ecor dMoni t or: MON- I ngr ess- per- DSCP- 0- 48- 11


Cache t ype: Synchr oni zed ( Pl at f orm cache)Cache si ze: 2000Cur r ent ent r i es: 8Hi gh Wat er mar k: 8


PFR SOURCE SI TE I D: 10. 8. 3. 3PFR DESTI NATI ON SI TE I D: 10. 2. 10. 10I P DSCP: 0x1AI NTERFACE I NPUT: Tu200POLI CY PERF MON CLASS HI ERARCHY: CENT- Pol i cy- I ngr ess- 0- 9: CENT- Cl ass- I ngr ess- DSCP-af 31- 0- 25t r ns counter packets expect : 130t r ns count er packet s l ost : 0t r ns bytes expected: 0


32/113

32

t r ns byt es l ost : 0t r ns one way del ay sampl es: 0t r ns one way del ay sum: 0appl i cat i on network del ay sampl e: 130appl i cat i on net work del ay sum: 46955rt p j i t t er i nt er arr i val sampl es: 130r t p j i t t er i nt er ar r i val sum: 83441counter byt es l ong: 9360

counter packets l ong: 130t i mest amp moni t or st art : 16: 14: 00. 000

PFR SOURCE SI TE I D: 10. 8. 3. 3PFR DESTI NATI ON SI TE I D: 10. 2. 10. 10I P DSCP: 0x20I NTERFACE I NPUT: Tu200POLI CY PERF MON CLASS HI ERARCHY: CENT- Pol i cy- I ngr ess- 0- 9: CENT- Cl ass- I ngr ess- DSCP-cs4- 0- 24t r ns counter packets expect : 131t r ns count er packet s l ost : 0t r ns bytes expected: 0t r ns byt es l ost : 0t r ns one way del ay sampl es: 0t r ns one way del ay sum: 0appl i cat i on network del ay sampl e: 131

appl i cat i on net work del ay sum: 47315rt p j i t t er i nt er arr i val sampl es: 131r t p j i t t er i nt er ar r i val sum: 74578counter byt es l ong: 9432counter packets l ong: 131t i mest amp moni t or st art : 16: 14: 00. 000

[ SNI P]

Branch10#

Notes:

Check Per-DSCP channel performance monitor cache records, include one-way-delay,

packet/byte loss, jitter metrics;

Metrics are aggregated per channel level;

Both smart-probe and data traffic flows are used for performance monitoring;

Threshold control Alerts (TCA) will be generated if there is violation for pre-defined performance

threshold.

6

Monitoring Operation

6.1 Monitor Site Prefix

Site-prefix is the database infrastructure for inside prefixes of all sites. Each local site learns site-prefixitself from egress performance monitor on external interface, and then publishes across all sites over

EIGRP SAF framework. Each local site subscribes to all remote site prefix service as well, so all sites share

one synchronized prefix database.

Check following table, there are four different type of prefix in this site-prefix database:


33/113

33

Local site-preifx with flag L: Local-learned prefix, here is the site-id, learned by egress site-

prefix monitor;

Local site-preifx with flag C: site-prefix configured by static site-prefix list, mostly on transit site;

Remote site-preifx with flag S: site-prefix learned from remote EIGRP SAF neigh ours;

Enterprise prefix with T: summary prefix defines the enterprise site-prefix boundary;

Example:

HubMC#show domai n one mast er si t e- pref i xChange wi l l be publ i shed bet ween 5- 60 secondsNext Publ i sh 00: 54: 41 l aterPr ef i x DB Or i gi n: 10. 8. 3. 3Pr ef i x Fl ag: S- From SAF; L- Lear ned; T- Top Level ; C- Conf i gur ed;

Si t e- i d Si t e- pref i x Last Updat ed Fl ag- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -10. 2. 10. 10 10. 1. 10. 0/ 24 00: 42: 07 ago S,10. 2. 10. 10 10. 2. 10. 10/ 32 00: 42: 07 ago S,

10. 2. 11. 11 10. 2. 11. 11/ 32 00: 18: 25 ago S,10. 8. 3. 3 10. 8. 3. 3/ 32 1d05h ago L,10. 8. 3. 3 10. 8. 0. 0/ 16 1d05h ago C,255. 255. 255. 255 *10. 0. 0. 0/ 8 1d05h ago T,- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -HubMC#

Br anch10#show domai n one mast er si t e- pref i xChange wi l l be publ i shed bet ween 5- 60 secondsNext Publ i sh 00: 53: 12 l aterPr ef i x DB Or i gi n: 10. 2. 10. 10Pr ef i x Fl ag: S- From SAF; L- Lear ned; T- Top Level ; C- Conf i gur ed;

Si t e- i d Si t e- pref i x Last Updat ed Fl ag- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -10. 2. 10. 10 10. 1. 10. 0/ 24 00: 00: 26 ago L,

10. 2. 11. 11 10. 1. 11. 0/ 24 01: 20: 47 ago S,10. 2. 10. 10 10. 2. 10. 10/ 32 01: 06: 49 ago L,10. 2. 11. 11 10. 2. 11. 11/ 32 01: 20: 47 ago S,10. 8. 3. 3 10. 8. 3. 3/ 32 01: 29: 07 ago S,10. 8. 3. 3 10. 8. 0. 0/ 16 01: 29: 07 ago S, C,255. 255. 255. 255 *10. 0. 0. 0/ 8 01: 29: 07 ago S, T,- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

HubBR1#show domai n one border si t e- pref i x

Pr ef i x Fl ag: S- From SAF; L- Lear ned; T- Top Level ; C- Conf i gur ed;

Si t e- i d Si t e- pref i x Last Updat ed Fl ag- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -10. 2. 10. 10 10. 1. 10. 0/ 24 00: 59: 12 ago S,10. 2. 11. 11 10. 1. 11. 0/ 24 01: 14: 42 ago S,10. 2. 10. 10 10. 2. 10. 10/ 32 01: 08: 04 ago S,10. 2. 11. 11 10. 2. 11. 11/ 32 01: 22: 01 ago S,10. 8. 3. 3 10. 8. 3. 3/ 32 01: 30: 22 ago S,10. 8. 3. 3 10. 8. 0. 0/ 16 01: 30: 22 ago S, C,255. 255. 255. 255 *10. 0. 0. 0/ 8 01: 30: 22 ago S, T,- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -HubBR1#

Br anch11#show domai n one bor der si t e- pref i x


34/113

34

Change wi l l be publ i shed bet ween 5- 60 secondsPr ef i x DB Or i gi n: 10. 2. 11. 11Pr ef i x Fl ag: S- From SAF; L- Lear ned; T- Top Level ; C- Conf i gur ed;

Si t e- i d Si t e- pref i x Last Updat ed Fl ag- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -10. 2. 10. 10 10. 1. 10. 0/ 24 01: 07: 46 ago S,

10. 2. 11. 11 10. 1. 11. 0/ 24 01: 21: 44 ago S,10. 2. 10. 10 10. 2. 10. 10/ 32 01: 07: 46 ago S,10. 2. 11. 11 10. 2. 11. 11/ 32 01: 21: 44 ago S,10. 8. 3. 3 10. 8. 3. 3/ 32 01: 30: 04 ago S,10. 8. 3. 3 10. 8. 0. 0/ 16 01: 14: 23 ago S, C,255. 255. 255. 255 *10. 0. 0. 0/ 8 01: 30: 04 ago S, T,- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Branch11#

Notes:

Site-prefix database is infrastructure, used for enterprise traffic-classes learning and routing-

control;

Site-prefix database is in sync across the PfRv3 domain for all master controller and borderrouters;

MCs publish local site prefixes to local BR and remote branch sites every 2 hours;

MCs subscribe and learn all remote site-prefix from EIGRP SAF service;

MCs and BRs age out all the site prefixes at a frequency of 24 hours;

Site-prefix monitor enabled on border router automatically:

Br anch10#show domai n one border pmi | begi n pref i x- l earnPMI [ Egr ess- pr ef i x- l ear n] - FLOW MONI TOR[ MON- Egr ess- pr ef i x- l ear n- 0- 48- 29]

moni t or - i nt er val : 30mi ni mummask- l engt h: 28key- l i s t :

i pv4 sour ce pr ef i xi pv4 source maskr out i ng vr f i nput

Non- key- l i st:counter bytes l ongcounter packets l ongt i mestamp absol ut e moni t ori ng- i nt erval st art


Expor t er - l i s t :10. 2. 10. 10

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Branch10#

Br anch10#show performance monitor cache monitor MON-Egress-prefix-learn-0-48-29 detailMoni t or: MON- Egr ess- pr ef i x- l ear n- 0- 48- 29


Cache t ype: Synchr oni zed ( Pl at f orm cache)


35/113

35

Cache si ze: 700Cur r ent ent r i es: 1Hi gh Wat er mar k: 1


I PV4 SRC PREFI X I PV4 SRC MASK I P VRF I D I NPUT bytes l ongpkts l ong t i me moni t or st art=============== ============= ============================= ======================================== ==================10. 1. 10. 0 / 24 0 ( DEFAULT) 172506717202 07: 55: 30. 000

Branch10#

HubBR2#show performance monitor cache monitor MON-Egress-prefix-learn-0-48-39 detailMoni t or: MON- Egr ess- pr ef i x- l ear n- 0- 48- 39


HubBR2#

Notes:

Local site-prefix monitor activated for site-prefix-learning-period (30 secs);

Site Prefix learned based on ipv4 source prefix and mask in CEF table;

Site-prefix learn based on egress traffic observed on external interface(UDP/TCP/ICMP flows);

exported to the local MC;

We must disable automatic site-prefix learning on transit site like DMVPN Hub site; any mistake

for site-prefix learning could result in unexpected results like traffic looping between sites due

to messed site-prefix database;

6.2

Monitor Traffic Class

Check Traffic-class learning and control. This has to be done on Master Controllers. Remember that all

Master Controllers are making local path decision, there is no Centralized MC making global decisions.

Start with the traffic-class summary to get a summary view of all traffic and how it is controlled as well

as their current path.

Here are the possible states for a Traffic Class:

UNCONTROLLED: No parent route is found

CONTROLLED: found a path that meets the criteria

OUT OF POLICY: No path meets the criteria set in the policy

Example:

HubMC#show domai n one mast er t r af f i c- cl asses summar y


36/113

36

APP - APPLI CATI ON, TC- I D - TRAFFI C- CLASS- I D, APP- I D - APPLI CATI ON- I DSP - SERVI CE PROVI DER, PC = PRI MARY CHANNEL I D,BC - BACKUP CHANNEL I D, BR - BORDER, EXI T - WAN I NTERFACEUC - UNCONTROLLED, PE - PI CK- EXI T, CN - CONTROLLED, UK - UNKNOWN

Dst - Si t e- Pf x Dst - Si t e- I d APP DSCP TC- I D APP- I D St ate SPPC/ BC BR/ EXI T

10. 1. 10. 0/ 24 10. 2. 10. 10 N/ A af 11 193 N/ A CN MPLS59/ 60 10. 8. 2. 2/ Tunnel 10010. 1. 10. 0/ 24 10. 2. 10. 10 N/ A cs1 192 N/ A CN MPLS57/ 58 10. 8. 2. 2/ Tunnel 10010. 1. 10. 0/ 24 10. 2. 10. 10 N/ A cs5 191 N/ A CN MPLS55/ NA 10. 8. 2. 2/ Tunnel 10010. 1. 10. 0/ 24 10. 2. 10. 10 N/ A ef 190 N/ A CN MPLS52/ NA 10. 8. 2. 2/ Tunnel 10010. 1. 10. 0/ 24 10. 2. 10. 10 N/ A af 41 195 N/ A CN I NET64/ 63 10. 8. 1. 1/ Tunnel 20010. 1. 10. 0/ 24 10. 2. 10. 10 N/ A cs4 189 N/ A CN I NET54/ 53 10. 8. 1. 1/ Tunnel 20010. 1. 10. 0/ 24 10. 2. 10. 10 N/ A af 31 194 N/ A CN MPLS61/ 62 10. 8. 2. 2/ Tunnel 100Tot al Traf f i c Cl asses: 7 Si t e: 7 I nt er net : 0

HubMC#

Notes:

Check destination Prefix (column Dst-Site-Pfx)

Check App Id if Application policies are used - Will N/A if DSCP based policies are used

Check DSCP value

Check the associated state - should be controlled (CN)

Check the path used - this is the path for all traffic going to this prefix with this DSCP value, i.e.

Traffic Class. In our example all performance based policies should go to the preferred path

MPLS.

Check the local Border Router used and the external exit used.

From there you can drill down and check individual Traffic Classes on master controller:

HubMC#show domain one master traffic-classes

Dst - Si t e- Pr ef i x: 10. 1. 10. 0/ 24 DSCP: af 11 [ 10] Tr af f i c cl ass i d: 193TC Lear ned: 00: 22: 13 agoPr esent St at e: CONTROLLEDCur r ent Per f ormance St atus: not moni t ored ( def aul t cl ass)Curr ent Servi ce Provi der: MPLS si nce 00: 12: 10Previ ous Ser vi ce Provi der: I NET f or 298 sec

BW Used: 9195 KbpsPresent WAN i nterf ace: Tunnel 100 i n Border 10. 8. 2. 2Present Channel ( pr i mary) : 59Backup Channel : 60Dest i nat i on Si t e I D: 10. 2. 10. 10Cl ass- Sequence i n use: defaul tCl ass Name: def aul tBW Updat ed: 00: 00: 14 agoReason f or Route Change: Load Bal ance


37/113

37

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Dst - Si t e- Pr ef i x: 10. 1. 10. 0/ 24 DSCP: cs1 [ 8] Tr af f i c cl ass i d: 192TC Lear ned: 00: 22: 14 agoPr esent St at e: CONTROLLEDCur r ent Per f ormance St atus: not moni t ored ( def aul t cl ass)Curr ent Servi ce Provi der: MPLS si nce 00: 12: 40Previ ous Ser vi ce Provi der: I NET f or 184 sec

BW Used: 9251 KbpsPresent WAN i nterf ace: Tunnel 100 i n Border 10. 8. 2. 2Present Channel ( pr i mary) : 57Backup Channel : 58Dest i nat i on Si t e I D: 10. 2. 10. 10Cl ass- Sequence i n use: defaul tCl ass Name: def aul tBW Updat ed: 00: 00: 12 agoReason f or Route Change: Load Bal ance

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Dst - Si t e- Pr ef i x: 10. 1. 10. 0/ 24 DSCP: cs5 [ 40] Tr af f i c cl ass i d: 191TC Lear ned: 00: 32: 43 agoPr esent St at e: CONTROLLEDCur r ent Per f ormance St atus: not moni t ored ( def aul t cl ass)Curr ent Servi ce Provi der: MPLS si nce 00: 32: 12

Previ ous Servi ce Provi der: UnknownBW Used: 3647 KbpsPresent WAN i nterf ace: Tunnel 100 i n Border 10. 8. 2. 2Present Channel ( pr i mary) : 55Backup Channel : noneDest i nat i on Si t e I D: 10. 2. 10. 10Cl ass- Sequence i n use: defaul tCl ass Name: def aul tBW Updat ed: 00: 00: 10 agoReason f or Rout e Change: Uncont r ol l ed t o Cont r ol l ed Transi t i on

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Dst - Si t e- Pr ef i x: 10. 1. 10. 0/ 24 DSCP: ef [ 46] Tr af f i c cl ass i d: 190TC Lear ned: 00: 37: 44 agoPr esent St at e: CONTROLLEDCur r ent Per f ormance St atus: i n- pol i cy

Curr ent Servi ce Provi der: MPLS si nce 00: 37: 13Previ ous Servi ce Provi der: UnknownBW Used: 5543 KbpsPresent WAN i nterf ace: Tunnel 100 i n Border 10. 8. 2. 2Present Channel ( pr i mary) : 52Backup Channel : noneDest i nat i on Si t e I D: 10. 2. 10. 10Cl ass- Sequence i n use: 10Cl ass Name: VOI CE usi ng pol i cy User - def i ned

pr i or i t y 2 packet - l oss- rat e threshol d 5. 0 per centpr i ori t y 1 one- way- del ay t hreshol d 150 msecpr i or i t y 2 byt e- l oss- r at e threshol d 5. 0 percent

BW Updat ed: 00: 00: 13 agoReason f or Rout e Change: Uncont r ol l ed t o Cont r ol l ed Transi t i on

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Dst - Si t e- Pr ef i x: 10. 1. 10. 0/ 24 DSCP: af 41 [ 34] Tr af f i c cl ass i d: 195TC Lear ned: 00: 22: 11 agoPr esent St at e: CONTROLLEDCur r ent Per f ormance St atus: i n- pol i cyCur r ent Servi ce Provi der: I NET si nce 00: 14: 07Previ ous Servi ce Provi der: MPLS f or 181 secBW Used: 5495 KbpsPresent WAN i nterf ace: Tunnel 200 i n Border 10. 8. 1. 1Present Channel ( pr i mary) : 64


38/113

38

Backup Channel : 63Dest i nat i on Si t e I D: 10. 2. 10. 10Cl ass- Sequence i n use: 20Cl ass Name: VI DEO usi ng pol i cy User - def i ned


BW Updat ed: 00: 00: 13 ago

Reason f or Rout e Change: Backup t o Pri mary path pr ef erence t r ansi t i on- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Dst - Si t e- Pr ef i x: 10. 1. 10. 0/ 24 DSCP: cs4 [ 32] Tr af f i c cl ass i d: 189TC Lear ned: 00: 37: 44 agoPr esent St at e: CONTROLLEDCur r ent Per f ormance St atus: i n- pol i cyCur r ent Servi ce Provi der: I NET si nce 00: 13: 13Previ ous Servi ce Provi der: MPLS f or 181 secBW Used: 7276 KbpsPresent WAN i nterf ace: Tunnel 200 i n Border 10. 8. 1. 1Present Channel ( pr i mary) : 54Backup Channel : 53Dest i nat i on Si t e I D: 10. 2. 10. 10Cl ass- Sequence i n use: 20Cl ass Name: VI DEO usi ng pol i cy User - def i ned


BW Updat ed: 00: 00: 14 agoReason f or Rout e Change: Backup t o Pri mary path pr ef erence t r ansi t i on

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Dst - Si t e- Pr ef i x: 10. 1. 10. 0/ 24 DSCP: af 31 [ 26] Tr af f i c cl ass i d: 194TC Lear ned: 00: 22: 12 agoPr esent St at e: CONTROLLEDCur r ent Per f ormance St atus: i n- pol i cyCurr ent Servi ce Provi der: MPLS si nce 00: 21: 41Previ ous Servi ce Provi der: UnknownBW Used: 9247 KbpsPresent WAN i nterf ace: Tunnel 100 i n Border 10. 8. 2. 2Present Channel ( pr i mary) : 61

Backup Channel : 62Dest i nat i on Si t e I D: 10. 2. 10. 10Cl ass- Sequence i n use: 30Cl ass Name: CRI TI CAL usi ng pol i cy User - def i ned

pr i or i t y 2 packet - l oss- r at e t hr eshol d 10. 0 per centpr i ori t y 1 one- way- del ay t hreshol d 600 msecpr i or i t y 2 byte- l oss- r at e t hr eshol d 10. 0 per cent

BW Updat ed: 00: 00: 11 agoReason f or Rout e Change: Uncont r ol l ed t o Cont r ol l ed Transi t i on

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Tot al Traf f i c Cl asses: 7 Si t e: 7 I nt er net : 0HubMC#

Notes:

Check present state

Check current and (if any) previous provider

Check the Traffic Class bandwidth

Check current WAN interface


39/113

39

Check present and backup channels. Performance measurements are extracted from channels.

You will not get performance directly from the traffic class itself.

Check that TC is correctly mapped to the policy

If a specific Traffic Class has experienced performance issues, you will be able to check it in the Traffic

Class report:

HubMC#show domai n one mast er t r af f i c- cl asses pol i cy VI DEO

Dst - Si t e- Pr ef i x: 10. 1. 10. 0/ 24 DSCP: cs4 [ 32] Tr af f i c cl ass i d: 200TC Lear ned: 00: 06: 00 agoPr esent St at e: CONTROLLEDCur r ent Per f ormance St atus: i n- pol i cyCur r ent Ser vi ce Provi der: MPLS si nce 00: 00: 30 ( hol d unt i l 59 sec)Previ ous Ser vi ce Provi der: I NET f or 117 sec( A f al l back pr ovi der . Pri mar y pr ovi der wi l l be r e- eval uat ed 00: 02: 30 l at er )BW Used: 309 KbpsPresent WAN i nterf ace: Tunnel 100 i n Border 10. 8. 2. 2Present Channel ( pr i mary) : 76Backup Channel : 73Dest i nat i on Si t e I D: 10. 2. 10. 10

Cl ass- Sequence i n use: 20Cl ass Name: VI DEO usi ng pol i cy User - def i nedpr i or i t y 2 packet - l oss- rat e threshol d 5. 0 per centpr i ori t y 1 one- way- del ay t hreshol d 150 msecpr i or i t y 2 byt e- l oss- r at e threshol d 5. 0 percent

BW Updat ed: 00: 00: 03 agoReason f or Route Change: Del ay

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Dst - Si t e- Pr ef i x: 10. 1. 10. 0/ 24 DSCP: af 41 [ 34] Tr af f i c cl ass i d: 199TC Lear ned: 00: 06: 01 agoPr esent St at e: CONTROLLEDCur r ent Per f ormance St atus: i n- pol i cyCur r ent Ser vi ce Provi der: MPLS si nce 00: 00: 00 ( hol d unt i l 89 sec)Previ ous Ser vi ce Provi der: I NET f or 148 sec( A f al l back pr ovi der . Pri mar y pr ovi der wi l l be r e- eval uat ed 00: 03: 00 l at er )

BW Used: 177 KbpsPresent WAN i nterf ace: Tunnel 100 i n Border 10. 8. 2. 2Present Channel ( pr i mary) : 75Backup Channel : 71Dest i nat i on Si t e I D: 10. 2. 10. 10Cl ass- Sequence i n use: 20Cl ass Name: VI DEO usi ng pol i cy User - def i ned


BW Updat ed: 00: 00: 01 agoReason f or Route Change: Del ay

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -Tot al Traf f i c Cl asses: 2 Si t e: 2 I nt er net : 0HubMC#

Notes:

Check Reason for recent Path Changes

Check Service provider re-evaluated timer for every 3 minutes;


40/113

40

All traffic-classes are synced to border router which perform routing-control based on traffic-class

database: show domain border traffic-classes

HubBR2#show domai n one bor der t r af f i c- cl asses

Src- Si t e- Pr ef i x: ANY Dst - Si t e- Pref i x: 10. 1. 10. 0/ 24DSCP: cs5 [ 40] Tr af f i c cl ass i d: 202TC Lear ned: 00: 09: 54 agoPr esent St at e: CONTROLLEDDest i nat i on Si t e I D: 10. 2. 10. 10I f _i ndex: 13Pri mary chan i d: 72Pr i mar y chan Pr esence: LOCAL CHANNELPri mary i nt erf ace: Tunnel 200Pr i mary Next hop: 10. 0. 200. 10 ( BGP)Backup chan i d: 78Backup chan Pr esence: NEI GHBOR_CHANNEL vi a border 10. 8. 2. 2Backup i nterf ace: Tunnel 0

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Src- Si t e- Pr ef i x: ANY Dst - Si t e- Pref i x: 10. 1. 10. 0/ 24DSCP: ef [ 46] Tr af f i c cl ass i d: 201TC Lear ned: 00: 09: 55 agoPr esent St at e: CONTROLLEDDest i nat i on Si t e I D: 10. 2. 10. 10I f _i ndex: 14Pri mary chan i d: 77Pr i mary chan Presence: NEI GHBOR_CHANNEL vi a bor der 10. 8. 2. 2Pri mary i nt erf ace: Tunnel 0Backup Channel not avai l abl e

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

Src- Si t e- Pr ef i x: ANY Dst - Si t e- Pref i x: 10. 1. 10. 0/ 24DSCP: cs4 [ 32] Tr af f i c cl ass i d: 200TC Lear ned: 00: 09: 55 agoPr esent St at e: CONTROLLED

Dest i nat i on

Pfrv3 Work Flow Guide

Documents

Transcript of Pfrv3 Work Flow Guide