Creating or editing an IPv4 block - BlueCat Integrity - 26.1.0

You must create at least one IPv4 block within a configuration. IPv4 blocks may contain additional blocks, so you can create a logical structure to group and arrange your IPv4 space.

1. Select the IPAM tab in the sidebar, then select IPv4 blocks.
   Note: To create or edit a block within a block, navigate to the parent block by selecting the parent block's range in the IPv4 blocks table, or by selecting the parent block in the IPAM tree view panel. Once you have navigated to the parent block, add the child block to the parent block's IPv4 blocks and networks table.
2. To create a new IPv4 block, select New. To edit an IPv4 block, select the row containing the IPv4 block in the table, then select Edit in the expanded details section.
3. Under General, set the following parameters:
   • Under Address definition, select a method to define the IPv4 block range:
     • CIDR block—enter the range in CIDR notation, such as 192.168.7.0/24. The new range must be fully contained within its parent. If the configuration is the parent object, you can specify any range.
     • Range—enter the Start address and End address of the range. The address range must conform to CIDR boundaries.
     • Address and netmask—enter the starting IP address and netmask in the Address and Netmask fields.
   • Name—enter a name for the block. This name is used only in Address Manager and isn't deployed to servers.
   • Location—select a location from the drop-down menu on which the IP object that you are adding or editing will be based. Blocks created within blocks will inherit the location of the parent block, unless a different location is specified at the block level here.
   • Default view—select a view from the list. The selected view is inherited by addresses within in the block. For IP addresses that are assigned to multiple views, the default view determines the view to which the IP address is assigned.
   • Template—select an IPv4 template to assign to the IPv4 block.
4. On the DNS restrictions tab, set the zones or views to restrict the IPv4 block to be used in:
   • Inherit restricted domains from parent—select the checkbox to inherit the parent object’s DNS restrictions. Selecting this option will autopopulate the Inherited restricted domains field with the names of restricted DNS zones and views defined in the parent object. Top-level blocks do not have restricted domains to inherit.

     Unselect the checkbox to display the Restricted domains field. In the Restricted domains field, enter the names of DNS zones and views to configure block-specific restricted domains settings.

   • Note:

     • Any DNS zone or view you add to the Restricted domains list is restricted for use only in the specified IPv4 block. The IPv4 block is also restricted for use only in the specified view(s) and zone(s).
     • You can't add an IPv4 block to a DNS zone if that DNS zone contains IP addresses outside of that IPv4 block.
5. On the Default domains tab, set the zones—containing domains—to be used when you are configuring the host name for an IPv4 address. The default domains help ensure accuracy when specifying the host name for an IPv4 address. When this is configured, you don't have to type the complete FQDN(s); you can select the name from a list of available domains.
   • Inherit default domains from parent—select the checkbox to inherit the parent object’s default domains. Selecting this option will autopopulate the Inherited default domains field with the names of DNS zones defined in the parent object. Top-level blocks do not have default domains to inherit.

     Unselect the checkbox to display the Default domains field. In the Default domains field, enter the names of DNS zones to configure block-specific default domains settings.

   • Note: If you set DNS restrictions in the DNS restrictions section, the default view and default domains must be located in the view and zone restrictions.

     The zones specified here will be available in the Host record field, when you are assigning an IPv4 address.

6. On the Assignment options tab, set the following options:
   • Duplicate name check—select Enable to prevent the use of duplicate host names in networks within the block, or select Disable to allow the use of duplicate host names.
     Tip:

     • When setting this option at a top-level block, only the Enable and Disable options are available.
     • When setting this option for a child block, the Inherited option is available. Select Inherited to have the block inherit the duplicate name check setting of its parent object. By default, all child blocks and networks inherit the duplicate name check setting.
   • Ping before assignment—select Enable to have Address Manager ping IP addresses before assigning them, or select Disable to have Address Manager assign addresses without checking their availability. When Address Manager pings an address and finds that it's in use, Address Manager indicates that the address is in use and can't be assigned.
     Tip:

     • When setting this option at a top-level block, only the Enable and Disable options are available.
     • When setting this option for a child block, the Inherited option is available. Select Inherited to have the block inherit the ping before assign setting of its parent object. By default, all child blocks and networks inherit the ping before assign setting.
7. On the DHCP alert settings tab, set the values for DHCP alerts:
   • Inherit watermark value from parent—when selected, the block inherits the DHCP alert settings from its parent object.

   • Low watermark (%)—triggers an alert when DHCP use falls below this value (when too few addresses are being used).

   • High watermark (%)—triggers an alert when a DHCP use rises above this value (when too many addresses are being used).

   Note: If you are using a shared network in DHCP, a DHCP alert notification for all networks inside the shared network will be sent as a single entity notification using the DHCP alert set at the configuration level. DHCP alerts for each individual network within any shared network will also be sent only if object-specific DHCP alerts are set at the network or DHCPv4 range level.
8. In the Change control section, add comments if required.
9. If creating an IPv4 block, select Create or Create and add another. If editing an IPv4 block, select Save.