PfRv3 manages aggregation of flows called traffic classes. A traffic class is an aggregation of flows destined to a destination prefix, that has a similar DSCP and application name (if application based policies are used). Traffic classes are learnt by monitoring traffic moving in egress direction on WAN interface.

The following figure explains Performance Monitor, depicted as 2.

Figure 1. Egress Performance Monitor

The local master controller performs the following functions:

The site-prefix mask length influences the traffic classes. The Site Prefix Splitting feature allows you to configure minimum mask length for traffic classes. This feature enhances the granularity of traffic classes. The granularity of traffic classes enables better load balancing by distributing the traffic classes among service providers in such a manner that each service provider’s egress interface bandwidth utilization is within 20 percent of each other. Thus, having more traffic classes will enable a better distribution of traffic among the service providers.

For example, the command ip route vrf green100.20.0.0255.255.0.010.20.0.310 translates to 100.20.0.0/16 in the site prefix database.

A site prefix splitting with a mask length of 24 would translate to the following list in the site prefix database:

100.20.0.0 /24
100.20.1.0 /24
100.20.2.0 /24
100.20.3.0 /24
100.20.4.0 /24

Perform this task to configure Site Prefix Splitting feature by using the minimum-mask-length enterprise value command.

domain default
vrf green
master hub
advanced
minimum-mask-length 24
minimum-mask-length enterprise 24

Use the following commands to verify site prefix splitting configuration:

• show domain default vrf green master status command on the master controller

• show domain default vrf green border status command on the branch router

HMCBR# show domain default vrf green master status
  *** Domain MC Status ***

 Master VRF: green

  Instance Type:    Hub
  Instance id:      1
  Operational status:  Up
  Configured status:  Up
  Loopback IP Address: 100.10.1.1
  Global Config Last Publish status: Peering Success
  Load Balancing:
   Admin Status: Disabled
   Operational Status: Down
   Enterprise top level prefixes configured: 0
  Route Control: Enabled
  Transit Site Affinity: Enabled
  Load Sharing: Enabled
  Mitigation mode Aggressive: Disabled
  Policy threshold variance: 20
  Minimum Mask Length Internet: 24          <<<< "Internet" added to the existing internet mml
  Minimum Mask Length Enterprise: 24        <<<< New line added for the enterprise mml
  Syslog TCA suppress timer: 180 seconds
  Traffic-Class Ageout Timer: 5 minutes
  Channel Unreachable Threshold Timer: 1 seconds
  Minimum Packet Loss Calculation Threshold: 15 packets
  Minimum Bytes Loss Calculation Threshold: 1 bytes

HMCBR# show domain default vrf green border status

Wed Oct 07 09:05:51.504
--------------------------------------------------------------------
  **** Border Status **** 

Instance Status: UP
Present status last updated: 00:03:14 ago
Loopback: Configured Loopback1 UP (100.10.1.1)
Master: 100.10.1.1
Master version: 2
Connection Status with Master: UP
MC connection info: CONNECTION SUCCESSFUL
Connected for: 00:03:08
Route-Control: Enabled
Asymmetric Routing: Disabled
Minimum Mask Length Internet: 24       <<<<
Minimum Mask Length Enterprise: 24     <<<<
Sampling: off
Channel Unreachable Threshold Timer: 1 seconds
Minimum Packet Loss Calculation Threshold: 15 packets
Minimum Byte Loss Calculation Threshold: 1 bytes
Monitor cache usage: 5000 (50%) Auto allocated
Minimum Requirement: Met
External Wan interfaces:
     Name: Tunnel10 Interface Index: 24 SNMP Index: 21 SP: ISP1 path-id: 1 Status: UP Zero-SLA: NO Path of Last Resort: Disabled 

Auto Tunnel information: 

   Name:Tunnel0 if_index: 32
   Virtual Template: Not Configured
   Borders reachable via this tunnel:  100.10.4.1 , 100.10.2.1 , 100.10.3.1
--------------------------------------------------------------------