Importing ranges - User Guide - BlueCat Horizon

BlueCat Horizon User Guide
ft:locale
en-US
Product name
BlueCat Horizon

In the Import data wizard, you can import range information with the following options:

  • Add range
  • Delete range
  • Modify range

Refer to the examples below to view the required format for each of these options.

When importing ranges (networks) into DDI orchestrator, the columns and fields should be formatted as follows:

Range column

There are three ways to identify the range to import. The first option is recommended. The other two options are offered for convenience when the date ranges span across two columns in the original spreadsheet.

  • 1. (Recommended) Include a Range column and provide the range in CIDR format, for example, 192.168.1.0/24, or from-to format, for example, 192.168.1.0-192.168.1.255. The Range column can alternatively be named Name, Network, Network range, IP range, IP Address range, or IPRange.
  • 2. Include Network_address and Network_mask columns, with the network address (for example, 192.168.1.0) and network mask (for example, 255.255.255.0) as values. This will be automatically converted to the CIDR format and displayed in a single Range column in the next step.
  • 3. Include from and to columns, with the from- and to- addresses of the range being imported.

Built-in fields

Format the following built-in fields as follows:

  • Container?: Identified in header line by either “isContainer”, “is_Container”, or “is Container”.

    If set to Yes, the range will be marked as a container. If set to No, it will be marked as a range/scope. If the field is left empty, it will not be updated. For more information about containers, refer to Creating containers.

  • Locked?: Identified in header line by “Locked”, “isLocked”, “is_Locked”, or “is Locked”.

    If set to Yes, the range will be locked. When a range is locked, IP addresses cannot be allocated from it in DDI orchestrator. If set to No, it will be unlocked. If the field is left empty, it will not be updated.

  • Allow auto-assignment of IP Addresses?: Identified in the header line by “AutoAssign”, “Auto-Assign”, “Auto_Assign”, or “Auto Assign”.

    If set to Yes, the auto-assignment of IP addresses will be enabled. If set to No, it will be disabled. If the field is left empty, it will not be updated.

  • Reserve Network and Broadcast Address?: Identified in the header line by “Subnet”, “isSubnet”, “is_Subnet”, or “is Subnet”.

    If set to Yes, the property will be enabled. If set to No, it will be disabled. If the field is left empty, it will not be updated.

Custom fields

In addition to the built-in fields for ranges, you can populate any custom fields defined for ranges with values as needed.

If there’s a conflict between the custom fields and the built-in fields, the custom field names take precedence. In such cases, an alternative must be selected for the built-in fields.

Examples

It's important to format the import data correctly. To read the general formatting guidelines, refer to Formatting the IPAM data for import. The following examples display the data format needed to import range information into DDI orchestrator:

Example 1: Adding ranges

This example creates imports two ranges, 1.2.3.0/24 and 1.2.4.0/24, with their respective titles and descriptions.

Range,Title,Description
1.2.3.0/24, My range, My first range to import
1.2.4.0/24, My range2, My second range to import
Example 2: Deleting ranges

This example deletes two ranges, 1.2.3.0/24 and 1.2.4.0/24.

Action,Range
Delete,1.2.3.0/24
Delete,1.2.4.0/24

Example 3: Modifying ranges

This example updates properties on the ranges 1.2.3.0/24 and 1.2.4.0/24.

Note: The mandatory Title column can be omitted when updating and will be left as-is, whether currently empty or not.
Action,Range,Location
Update,1.2.3.0/24, US
Update,1.2.4.0/24, US