Import Easy IP subnet and IP address exports

Easy IP

Overview

LightMesh recognises Easy IP CSV exports and maps their columns automatically on Configuration > Imports. You upload the files as they come out of Easy IP — you do not rename headers or join the address and mask columns yourself.

A migration uses two imports (one file per wizard run), in this order:

  1. Subnet export — each subnet’s address and mask become a LightMesh subnet; its comment becomes the description.
  2. IP address export — each IP is placed in its subnet, which LightMesh works out from the address and mask.

Both files land in the Default zone unless you add a Zone column (same name on both files). See Use a zone other than Default.

Permission required: Imports require an app role of Owner, Administrator, or Contributor. See Roles & RBAC for details.

For the shared wizard (drafts, validation errors, Save for review), see Import a spreadsheet.

Prerequisites

  • A subnet export and an IP address export from Easy IP, saved as CSV (Excel with the same headers also works).
  • Optional: IP address custom fields named Owner, Email Address, Telephone Number, and Location if you want to keep Easy IP owner details. See Keep owner details.

Want to try first? Download the documentation-only examples:

How Easy IP columns import

LightMesh detects the format from the headers. Header case and separators do not matter (SHORT_SUBNET and Short Subnet both match).

Subnet export

Detected when the file has SHORT_SUBNET, CIDR_MASK, and COMMENT.

Easy IP column Imports as Example
SHORT_SUBNET + CIDR_MASK Subnet (CIDR) 192.0.2.0 + 24 → 192.0.2.0/24
COMMENT Description Head office LAN

IPv4 and IPv6 subnets can be mixed in the same file.

IP address export

Detected when the file has SHORT_IP_ADDRESS, CIDR_MASK, and HOST_NAME.

Easy IP column Imports as Example
SHORT_IP_ADDRESS IP Address 192.0.2.10
SHORT_IP_ADDRESS + CIDR_MASK Subnet (CIDR), worked out per row 192.0.2.10 + 24 → 192.0.2.0/24
HOST_NAME Host Name fs-hq-01
MAC_ADDRESS MAC Address 00:1A:2B:3C:4D:10
DEVICE_TYPE Resource Type Server
NOTES Notes File server
OWNER, EMAIL_ADDRESS, TELEPHONE_NUMBER, LOCATION Custom fields with those names, if they exist Rack A1
ADDRESS_TYPE Not imported

The IP address export has no zone or subnet column. Zone-less rows go into Default, which is also where the subnet import puts zone-less subnets — so each IP attaches to a subnet you imported first.

Step 1: Import the subnet export

  1. Go to Configuration > Imports → + New Import.
  2. Select Subnets, name the import (for example Easy IP — subnets), and click Next.
  3. Choose create-only or create-and-update, then upload the Easy IP subnet CSV.
  4. On Map columns, confirm the blue notice Easy IP subnet export recognised. Columns should map to Subnet, CIDR Mask, and Description.

Easy IP subnet export recognised

  1. Click Next. Validation should show valid rows ready to import.

Easy IP subnets validated

  1. Click Continue, choose Publish now (or Save for review), then Publish.

Easy IP subnets summary

Easy IP subnets published

Imported subnets appear in CIDR form in the Default zone. IPv6 is stored compressed lowercase (for example 2001:db8:0:100::/56).

Subnet names: Easy IP subnet exports do not include a name. Add a Name column before upload, or name subnets later in LightMesh.

Step 2: Import the IP address export

  1. + New Import again → select IP Addresses → name it (for example Easy IP — IP addresses) → Next.
  2. Upload the Easy IP IP address CSV.
  3. On Map columns, confirm Easy IP IP address export recognised. Owner columns without a matching custom field stay unmapped (Select a field) until you map them or create the fields.

Easy IP IP address export recognised

  1. Validate, then publish.

Easy IP IP addresses validated

Easy IP IP addresses published

Each IP is saved in the subnet worked out from its address and mask (for example 198.51.100.130 with mask 26 → 198.51.100.128/26).

Keep owner details

Easy IP column Custom field name
OWNER Owner
EMAIL_ADDRESS Email Address
TELEPHONE_NUMBER Telephone Number
LOCATION Location

Create the fields under Configuration → Schema before you upload the IP address file. See Custom Field. Values are read as text, so phone numbers keep leading zeros.

Use a zone other than Default

Both Easy IP files import into Default. To use another zone, add a Zone column with the same zone name to both files before uploading. LightMesh creates the zone if needed and matches each IP to a subnet in that zone.

Mask formats

CIDR_MASK accepts:

  • A prefix length: 24 or /24
  • An IPv4 netmask: 255.255.255.0

IPv6 masks must be a prefix length from 0 to 128. Columns named CIDR Mask, Netmask, or Prefix Length map to CIDR Mask automatically (not only for Easy IP).

Troubleshooting

When validation finds problems, LightMesh shows a red banner and grouped issues. Open the Errors tab, then Exclude rows you want to skip, or fix the CSV and run a new import. Continue stays disabled while error rows remain.

Easy IP validation with a bad mask

Message / situation What to do
CIDR Mask out of range (for example 40 on IPv4) Correct the mask in that row (0–32 for IPv4, or a valid netmask).
Address already has a prefix that disagrees with CIDR_MASK Remove one of them or make them match.
IP address is not valid, so its subnet cannot be worked out Fix the IP in that row.
Already exists Those subnets or IPs are already in LightMesh. Exclude them, or use create-and-update if you meant to refresh fields.
No Easy IP … recognised notice A detection header is missing or renamed. Check How Easy IP columns import, or map columns by hand.
IP addresses do not land in the imported subnets Import the subnet file first, and use the same zone on both files.
Owner columns are not imported Create matching IP address custom fields, then import again.
Previous
Next