Manual Chapter : Enforcing Bandwidth Control Provisioned by PCRF
Applies To:Show Versions
- 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0
Enforcing Bandwidth Control Provisioned by PCRF
Overview: Enforcing bandwidth control provisioned on PCRF
Policy Enforcement Manager™ (PEM) can enforce bandwidth limits provisioned by the PCRF using dynamic PCC rules. You do this by creating a dynamic bandwidth controller with the name
dynamic_spm_bwc_policy. This bandwidth controller must be created on the BIG-IP system® using this predefined name. It does not need to be associated with an enforcement policy in PEM. Subscribers are assigned bandwidth in proportion to their configured rates. So for example, if subscriber A is assigned 4Mbps, and B is assigned 8Mbps, B will always get twice the bandwidth that A gets.
Creating a dynamic bandwidth control policy for PCRF
To set up bandwidth control through PCRF, you must have bandwidth control rules configured on the PCRF.
You can create a dynamic bandwidth controller so that PEM can enforce the maximum bit rate configured on the PCRF. You must follow the steps exactly as described here using the specified name for the bandwidth controller, and you must create the associated categories.
- On the Main tab, click.
- In theNamefield, type the namedynamic_spm_bwc_policy.
- In theMaximum Ratefield, type a number and select the unit of measure to indicate the total throughput allowed for the resource you are managing.The number must be in the range from1 Mbpsto1000 Gbps. This value is the amount of bandwidth available to all the connections going through this static policy.
- From theDynamiclist, selectEnabled.The screen displays additional settings.
- In theMaximum Rate Per Userfield, type a number and select the unit of measure.For example, use50Mbps.The number must be in the range from 1Mbps to 2Gbps. However, the value you use is just a place holder and is never used by the system. For this example, the value is overridden by the PCRF.
- Enable theMeasuresetting, if you want to measure bandwidth on all future instances of this bandwidth control policy.The system measures bandwidth with the frequency you specify in theLog Periodsetting, and sends it to the log publisher you specify using theLog Publishersetting.
- Leave theIP Marking (TOS/DSCP)andL2 Marking (802.1p)values set toPass Through, the default value.
- After you finish configuring the bandwidth controller, theBandwidth Controllersscreen opens.
- Click the Bandwidth Control policy name, that you configured.The Bandwidth Controllers policy page opens.
- In theCategoriesfield, add up to 32 categories of traffic that this bandwidth control policy manages.All the categories share the specified bandwidth, in accordance with the rate specified for each category.Use theCategoriessetting only if you have not set values for theIP Marking (TOS/DSCP)or theL2 Marking (802.1p)setting.
- In theCategory Namefield, type a descriptive name for the category.
- In theMax Category Ratefield, type a value to indicate the most bandwidth that this category of traffic can use, and select the unit of measure from the list, or select%and type a percentage from1to100.If you specify a rate, the number must be in the range from500 Kbpsto the rate specified for theMaximum Rate Per Usersetting. A percentage indicates that this category can use up to the specified percentage of the maximum per-user rate. These values are upper limits (not minimum or guaranteed), so the sum can exceed the value you specified for theMaximum Rate Per Usersetting.
- From theIP Marking (TOS/DSCP)list, selectSpecifyand type a number between0and63to assign a Type of Service (ToS) level to packets that exceed theMax Category Rate.If you do not want to set a ToS level, maintain the default setting,Pass Through.
- From theL2 Marking (802.1p)list, selectSpecifyand type a number between0and7to assign a Quality of Service (QoS) level to packets that exceed theMax Category Rate.If you do not want to set a QoS level, maintain the default setting,Pass Through.
If this is the first bandwidth control policy created on a BIG-IP device, the system also creates a default static bandwidth control policy named
default-bwc-policyto handle any traffic that is not included in the policy you created. If you delete all bandwidth controllers, this policy is also deleted.
For PEM to enforce bandwidth control, you need to create a listener (Policy Provisioning and Online Charging Virtuals) with a Gx interface configured.
Creating a listener for subscriber discovery and policy provisioning
You can create listeners that specify how to handle traffic for policy enforcement. Creating a listener does preliminary setup tasks on the BIG-IP system for application visibility, intelligent steering, bandwidth management, and reporting. You can also connect with a Policy and Charging Rules Function (PCRF) over a Gx interface.
- On the Main tab, click.The Control Plane Listeners page opens.
- In the Policy Provisioning and Online Charging Virtuals area, clickAdd.The New Configure Diameter Endpoint Provisioning and Online Charging screen opens.
- In theNamefield, type a unique name for the listener.
- In theDescriptionfield, type a description of the listener.
- For theVLANs and Tunnelssetting, move the VLANs and tunnels that you want to monitor from theAvailablelist to theSelectedlist.
- To connect to a PCRF, from theDiameter Endpointlist, selectEnabledand selectGxorSdfrom theSupported Appsoptions.
- In theProduct Namefield, type the product name which is used to communicate with the PCRF.
- In theOrigin Hostfield, type the fully qualified domain name of the PCRF or external policy server, for example,ocs.xnet.com.
- In theOrigin Realmfield, type the realm name or network in which the PCRF resides, for example,xnet.com.
- In theDestination Hostfield, type the destination host name of the PCRF or external policy server, for example,pcrfdest.net.com.
- In theDestination Realmfield, type the realm name or network of the PCRF, for example,net.com.
- For thePool Member Configurationsetting, add the PCRF servers that are to be members of the Gx endpoint pool. Type theMember IP AddressandPortnumber, then clickAdd.
- In theMessage Retransmit Delayfield, type the number of milliseconds to wait before retransmitting unanswered messages in case of failure from the BIG-IP system to the PCRF over the Gx interface. The default value is1500.
- In theMessage Max Retransmitfield, type the maximum number of times that messages can be retransmitted from the BIG-IP system to the PCRF. The default value is2.
- In theFatal Grace Timefield, type the time period in seconds that a diameter connection can remain disconnected before the system terminates all sessions associated with that diameter endpoint. The default value is500.
- ClickFinished.The Policy Enforcement Manager creates a listener.
When you create a listener, the Policy Enforcement Manager also creates virtual servers for each type of traffic (TCP, UDP, or both), and a virtual server for HTTP traffic. The system sets up classification and assigns the appropriate policy enforcement profile to the virtual servers. The system also creates a virtual server for the Gx interface with a diameter endpoint profile. If you are connecting to a RADIUS authentication server, a virtual server for RADIUS is also added.
When traffic flows through the BIG-IP® system, the system limits the aggregated bandwidth for all subscribers to the
Maximum Ratespecified in the
dynamic_spm_bwc_policybandwidth control policy. The PCRF provides the
Maximum Rate Per Userfor each subscriber, overriding the value in the bandwidth control policy. Policy Enforcement Manager™ restricts subscribers to the maximum user rate, and bandwidth is spread among subscribers fairly, on a best effort basis.