Navigate to Network > BMU Overview. Click in the action column and select Configure BMU. You will be presented with the BMU configuration screen. All changes made in this section will be pushed to the BMU in real time. The available tabs are IPv4 Address Ranges, IPv6 Address Ranges, Open Access List, BMU Details, Configurations (Powercode BMUs only) and Event Log. Procera, MikroTik and Saisei BMUs also have a Slave BMUs tab. Link BMUs have a Link Health tab and no Configurations tab; see Link BMU. Which tabs you see also depends on your permissions.
The IPv4 Address Ranges tab defines all of the address ranges you will be configuring customer equipment in. Any devices that pass through the BMU that do not fit into one of these ranges will either be allowed or denied depending upon the Default Behavior setting in your BMU. Generally, you will want to configure every address range here that will be used on the network the BMU will be controlling. Click Add New IPv4 Address Range to add a new range. You will be presented with a form containing the following fields:
If you have enabled DHCP for this range, the additional options are as follows:
The IPv6 Address Ranges tab holds the IPv6 pools for this BMU. Click Add New IPv6 Address Range to add one. The fields are covered in Configuring IPv6 Addresses.
The open access list is a list of IP addresses that users should always be able to access, regardless of their account status. If you use ProPay as your payment gateway, please make sure you enter 192.41.97.89 and 63.232.62.209 as open access entries to ensure customers can always be redirected to the ProPay tokenization portal.
The BMU details tab is purely informational and contains some details on the BMU.
This tab is only on Powercode BMUs. Every 10 minutes, Powercode checks with the BMU to see if any configuration changes have been made. If so, a copy of the configuration is pulled into Powercode and stored so you can restore it at a later date if needed.
The event log contains a list of all changes made to the BMU. The exception to this is if you are modifying a Procera PRE BMU rather than a Powercode BMU. If this is the case, you will not have the configurations tab and you will have an additional tab labeled Slave BMUs. When using a Procera PRE, you generally will want to associate one or more slave Powercode BMUs with the Procera BMU as the Procera cannot provide DHCP for the network and it cannot proxy the real time and historical monitoring queries to the network. If you are using a Procera PRE, navigate to the slave BMUs tab and add a slave BMU. The default behavior of this BMU should also be set to Slave. This Powercode slave BMU can now be installed in the network out of line and it will provide DHCP and network monitoring services. If you add multiple slave BMUs, all network monitoring probes will be shared fairly between the slaves in order to expedite network monitoring.