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 IP Address Ranges, Open Access List, BMU Details, Configurations and Event Log.
IP Address Ranges
The IP 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 IP Address Range to add a new range.
You will be presented with a form containing the following fields:
- Name: Enter a descriptive name for the range here.
- Start IP Address: Enter the first IP in this range that will be used to assign equipment.
- End IP Address: Enter the last IP in this range that will be used to assign equipment.
- Whitelist: If this is disabled, any devices in this range that are not configured in Powercode will be denied access. If it is enabled, all users will be allowed access in this range regardless of their Powercode configuration.
- Parent ID: Entering the ID of a specific piece of equipment here will automatically associate all devices in this range with the parent device using the parent -> child system.
- DHCP Server: Selecting Enabled will instruct the BMU to run DHCP for this range. You will then be presented with additional DHCP configuration options.
If you have enabled DHCP for this range, the additional options are as follows:
- Default Gateway: Enter the default gateway that users should be provided with if they are in this range.
- DNS Servers: Enter the DNS server address IPs you wish to have provided via DHCP.
- Subnet Mask: Enter the subnet mask for this range.
- Lease Time: Enter the number of seconds for the DHCP lease. This defaults to 86400, 1 day.
- Range Mode: Enter Static if you only wish customers to receive an IP in this range if they are explicitly configured in Powercode. Select Dynamic if this will be a catch-all range that customers will be assigned an IP from if they are not configured in Powercode. You cannot add customers into a dynamic range – therefore, most ranges will be Static.
- Shared Network: If this range exists on a router other than the BMU (e.g. if the BMU is at the core of the network and this subnet will be provided on a remote router via DHCP relay) you must group all subnets for that remote router into a single shared network. You can create a new shared network or use an existing one. For example, if you have a router at a network location named ‘Greenfield’ and that router has 3 subnets on it that the BMU will provide DHCP for, you should create a shared network named ‘Greenfield’ and associate all three subnets with that shared network.
- DHCP Options: If you have equipment that requires DHCP option 2 or 4, enter the appropriate data into these fields. Otherwise, leave them blank.
Open Access List
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.
BMU Details
The BMU details tab is purely informational and contains some details on the BMU.
Configurations
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.
Event Log
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.