Simple Upload / Import from CSV
The Upload / Import from CSV tool is used if you have a simple .csv file with IP block information, such as CIDR, mask, ASN, RIR, etc. It is accessed from the Data Import Tab from the Admin section.
To import your IP block information, follow the following steps:
The Import from CSV tool will create Top-Level Aggregates and place blocks under those aggregates based on the following method:
First, the importer will parse through the provided data, order all blocks from largest to smallest, then attempt to split the largest block out of an existing block matching the IP space and RIR. If that fails (no larger block exists), then that block is added in the system as its own Top-Level-Aggregate. Subsequent blocks will undergo the same process.
This method ensures that your list of IP blocks does not need to be organized in any particular order.
If your import includes a large number of small blocks (/30s, /32s), be sure you've included at least one large block which encompasses them (/24, /22). This will ensure that the smaller blocks are neatly organized under the larger block, rather than imported as their own Top-Level Aggregates. |
The Upload / Import from CSV tool requires only a .csv file for importing.
Be sure to review "Preparing Data for Import" on the Importing your Data page before you begin. Verify that your .csv is correctly parsed and cleanly formatted with your IP block information (using your choice of the available field list shown below), and is UTF-8 encoded for best results.
Common normalization steps required for IP imports include:
To ensure correct importing of any special characters, make sure to use UTF-8 encoding for your CSV file! |
This tool supports the following fields:
 |
For IP Import from .csv, the following fields are REQUIRED:
All other fields are optional. |
Navigate to the Data Import Tab from the Admin button. Select "Upload / Import from CSV" under "IP Import".
Create a Job Name and Description for the import. This is especially useful to keep track of progress in cases the data arrives from multiple sources, or will require multiple stages of manual review.
Select the .csv file that you prepared above by selecting the "Choose File" button, and browsing to the correct file location. Then hit "Start Import".
Although you cannot add new files to an existing job, for jobs with multiple sources for data (which may have different formatting), you can simply create separate jobs and descriptions for each source - no need to manually combine the data into one file before importing. The Import tool's mapping and editing functions will allow for the data to be reconciled in ProVision. For large data sets where multiple stages of manual review might be needed, you can create a new job using the same set of data files in order to work in parallel on a different portion of the data. |
After importing, the new job will appear under the "Existing Jobs" section. To continue working with this job, select it from the list (by clicking on the job name) and the next step will appear on the page.
Using the dropdown menu above each data field, select the appropriate definition for each of the imported columns.
Other columns which do not apply under the available definitions should be left as blank, and will be skipped during the upload process.
When completed, hit "Next".
If references exist in your data that do not currently exist in ProVision (such as new tags or resources) the import tool will alert you to the missing references, and give you the option to create those references in ProVision. If you wish to add these elements, select the checkboxes next to the element and click the "Add (Element name)" button below.
If your .csv has a header row as the first line, that row may give information that produces a missing reference notice - such as "Tag", "Region", "Block", and so forth. If this is the case, simply uncheck that item and add only the desired references. |
In this example, we get a notification that we are missing a tag named "Tags". However, we know by looking at our data that is simply an item that was part of the header line in the .csv, so we want to bypass this step.
After supplying the file and defining columns, a review step is provided. Records with errors will show as color coded, and can be filtered to be viewed by All, Valid, Warnings, Invalid, or Ignored.
From here, the records can be edited or ignored. Select "Ignore" for records that you do not wish to import at this time. Records that are Ignored or Invalid will automatically be skipped.
If your .csv has a header row as the first line, that row will be shown as the first record in review data as well. Simply click "Ignore" on the first record to disregard the row. |
If warnings or invalid entries are found, you may edit the data by clicking the "Edit" button.
Here you can edit the invalid field, or add /change information for any other available field.
After editing, hit "Save". If the edits are valid, the background color for the data row will be white.
Continue reviewing and editing data as desired. When done, proceed to Step 4.
When the review step is completed, hit the "Execute Import" button. A progress bar will appear to show progress and note errors if they occur.
When the bar reaches 100%, the import is complete. The Data Review section will show which data rows were successfully imported.
After the Import is complete, there are a few followup options for working with the import job or imported blocks. We recommend:
If the IP Import was fully successful, and you do not wish to retain the job data, the Import Job may be deleted from the "Existing Jobs" list by clicking the delete button next to the job name.
Deleting an import job is permanent and non-recoverable! When working with large or sensitive import jobs, consider performing a backup of your instance before and after the import job as a safeguard. |
See the following areas for information on working with IPAM / IP Blocks post-import: