02-10-2016 01:44 AM
We have a huge number of fixed addresses for which I need to individually update one particular custom EA, called 'Faceplate'.
The EA is unique on each address.
I'm pretty new to this but can easily create a csv containing the information but it's getting it into a format that Infoblox likes that I'm struggling with.
In testing I got as far as this but it's not keen.
header-FixedAddress, ip_address*, EA-Faceplate
FixedAddress, 192.168.210.3, KV-732
What multitude of things am I missing?
Any help greatly appreciated
02-10-2016 03:12 AM
All you need is another column for "mac_address" with the values in the following format - 11:22:33:44:55:66.
If you don't know the MAC address, then you can use all zeroes but that would indicate that it becomes a Reservation, not a Fixed Address (in the sense of providing a DHCP service).
02-12-2016 04:38 AM
Thanks for the reply. We don't use the MAC addresses for the Fixed Address but the Circuit ID from the DHCP Relay Agent. Does that change what I need to do?
02-14-2016 03:19 PM
DHCP relay agent? Are these static (fixed addresses) or dynamic?
If they are fixed addresses, meaning you have provisioned them through the GUI (or API or CSV upload), then add the additional column as mentioned. If dynamic, you'll have to export all the addresses for which you want to make a change, then re-import them again in CSV. Not sure if this is a good idea though given a dynamic lease may disappear after the lease expires.
Go to the Infoblox support site and download the CSV import guide for syntax.
02-18-2016 12:23 AM
Hi, yes they are fixed addresses. We assign an IP to each physical network port and use the circuit ID to make sure they get that IP.
02-22-2016 03:28 AM
I've tried this with adding the 00:00... mac address line. The EAs update as expected but it converts to a reservation and removed the Circuit ID from the Fixed Address, which I think is what you were saying would happen.
Is there a header for Circuit ID I need to use to maintain these as Fixed Addresses whilst amending the faceplate?
02-22-2016 11:00 AM - edited 02-22-2016 11:05 AM
Do a CSV export of the fixed addresses you have in the database already.
that should show how the name the columns to match the data & circuit ID.
there is a field 'circuit_id' and according the the CSV import reference : "This field is required when match_option = CIRCUIT_ID"
So you need both the 'circuit_ID' and 'match_option' columns in your import