Powercode supports the use of a Procera PRE as a BMU in Powercode. Utilizing a Procera PRE also allows you to control your customers on a per-application basis, rather than simply rate limiting their connection.
When adding a Procera PRE to Powercode as a BMU, Powercode will take over the majority of the configuration of the device. Please do not attempt to modify or reconfigure the objects created by Powercode using the PacketLogic client as this may cause significant issues when Powercode attempts to make updates to the PRE. You are welcome to create other objects and rules still, as long as you understand how they will affect the existing Powercode objects.
- The Procera PRE has no native bursting configuration. This means any burst rates configured in Powercode will be ignored.
- Devices that have usage tracking disabled will not be rate limited. Make sure you have usage tracking enabled on any device types you want to be rate limited.
Create a user in the Procera PRE with a username of powercode. This user should have full access rights to the PRE. Navigate to Network -> BMU Overview and select Add New BMU. Set the BMU Type to Procera. You will now be presented with two new options – redirect IP and default behavior.
The redirect IP is the IP that users will be redirected to if they are unauthorized. This is typically your billing server. Do not enter http://, just the IP address. Default Behavior is how you want to handle unknown connections. If you set this to Allow, then any IP that is not configured in Powercode will be allowed network access. If you set this to Deny, then any IP that is not configured in Powercode will be redirected. Please note that if you are adding a PRE to Powercode for the first time, you should set this behavior to Allow, otherwise the unconfigured PRE will begin blocking all traffic.
Powercode defines an unknown IP as an IP that is within a subnet that is not defined in Powercode. Please note that if you define a subnet and disable whitelisting, that subnet is now known and any unauthorized devices within that subnet will be redirected.
After adding the PRE, wait a few seconds and the status will change to Good. If it does not, validate the IP address and the password for the powercode user.
After adding the PRE, select Configure from the action drop down. You should now add all the IP address ranges you want the PRE to handle. If you do not want unauthorized customers in these ranges to be redirected yet, make sure you set Whitelist to Yes.
One major difference with the Procera PRE is that it cannot run DHCP or network monitoring. You must add a slave Powercode BMU to the PRE in order for these services to be available. To add a slave BMU, navigate to the Slave BMUs tab and add a Powercode BMU to the list. You should also login to the BMU web interface, navigate to System -> Powercode Settings and set the default behavior on the slave BMU to Slave.
Now, when users are provisioned in a subnet that is associated with the Procera PRE, this BMU will provide DHCP and network monitoring services for them. The slave BMU does not need to sit inline in the network.
After completing configuration, synchronize the PRE. If you look at the rule configuration using the PacketLogic client, you will now see a number of net objects, shaping objects and shaping rules. Do not modify these rules directly. The configuration of these rules is pulled from Powercode – making changes in Powercode will update them immediately.
You can configure customized shaping rules directly in Powercode. Please refer to the Procera Shaping Rules article for more details.
Once you are done configuring your PRE from within Powercode, you can switch the default behavior to Deny.
Since Powercode utilizes dynamic net objects in the Procera PRE, you cannot examine the net objects directly to determine which customers are associated with each net object. However, you can diagnose problems from within Powercode. Under Network -> BMU Overview, select Diagnostics from the drop down. You will now be able to examine each net object and see all dynamic net objects associated with the net object from within the Powercode interface. This is only needed if you believe the configuration of the PRE is incorrect.