Splitting Subnets Between Beacons
FlexNet Manager Suite ()
The normal practice is to assign subnets reported by Active Directory directly to your inventory beacon(s); but what if a subnet contains well over 10,000 devices? You can use this concept to spread the load across multiple inventory beacons.
Suppose that Active Directory reports that site Production contains a subnet 10.200.0.0/16, and that this subnet contains so many active devices that you need to split the load across two (or more) inventory beacons. The overall concept is to:
- In the web interface for FlexNet Manager Suite, disable the actual subnet reported by Active Directory. Disabled subnets cannot be used for inventory collection, and do not appear in the list of unassigned subnets.
- Manually create two (or more) new subnet records that divide up the address space between them.
The subnet mask allows you to divide up the address space, and the base subnet address can be specified to move each new subnet above its neighbor.
The required settings are illustrated in the following:
| Source | Subnet | Site | Status | Automatically managed | Assigned to beacon |
|---|---|---|---|---|---|
| Active Directory | 10.200.0.0/16 | Production | Disabled | Checked | None |
| Manual entry | 10.200.0.0/17 | Production | Enabled | Clear (AD imports do not remove) | BeaconA |
| Manual entry | 10.200.128.0/17 | Production | Enabled | Clear (AD imports do not remove) | BeaconB |
**Parent topic:**Assigning Sites and Subnets to a Beacon