...
- The Object Change Tracking feature is optimized to reduce impact on the DDI services and it runs only on the Grid Master. The synchronization process synchronizes 1000 objects at a time with a 2 second pause in between. There might be a slight impact on the Grid Master Candidate as they get updates from the Grid Master. When protocol services are running on the Grid Master Candidate you might encounter a 5% drop in the protocol performance. This feature does not impact the services that are running on the Grid members.
- NIOS does not update the sequence ID of the respective parent when you modify a child object. For example, inserting an A record under DNS zone does not increase the sequence number of the zone object.
- When you delete a parent object, NIOS saves the child objects in the deleted object table. But, if the associated child objects are either resource records or leases, NIOS will neither save them in the deleted object table nor update the sequence ID for these child objects.
- If you update a parent object, then the sequence ID of its child objects will not change.
- NIOS updates the sequence ID of the host record and IPv4 and IPv6 host addresses, if there are any changes to host addresses, both IPv4 and IPv6. The sequence ID is also updated when you update the host alias records that results in increase in the sequence ID of the host record and all its child objects.
...
For
...
example,
...
if
...
you
...
create
...
a
...
host
...
record
...
hhh.test.com
...
with
...
an
...
IPv4
...
address
...
and
...
perform
...
an
...
incremental
...
synchronization
...
to
...
get
...
updates,
...
the
...
response
...
contains
...
an
...
updated
...
host
...
record
...
and
...
host
...
address:
...
curl
...
-k1
...
-u
...
admin:infoblox
...
-H
...
content-type:application/json
...
-X
...
GET
...
https://10.32.2.202/wapi/v2.5/db_objects?start_sequence_id=2830689052:0\&object_types=
...
record:host,record:host_ipv4addr\;_return_fields=last_sequence_id,object,object_type\;
...
_return_type=json-pretty
...
The
...
response
...
is
...
as
...
follows:
...
[ { "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDIw:38",
...
"object":
...
{
...
"_ref":
...
"record:host/ZG5zLmhvc3QkLl9kZWZhdWx0LmNvbS5rYXJqYWdpLmhvc3Qx:
...
hhh.test.com/default",
...
"ipv4addrs":
...
[
...
{ "_ref":
...
"record:host_ipv4addr/ZG5zLmhvc3RfYWRkcmVzcyQuX2RlZmF1bHQuY29tLmthcmphZ2kuaG9zdDEuMS4x
...
LjEuMS4:1.1.1.1/
...
hhh.test.com/default",
...
"configure_for_dhcp":
...
false,
...
"host":
...
"
...
hhh.test.com",
...
"ipv4addr":
...
"1.1.1.1",
...
"mac":
...
"11:11:11:11:11:11"
...
} ],
...
"ipv6addrs":
...
[
...
{ "_ref":
...
"record:host_ipv6addr/ZG5zLmhvc3RfYWRkcmVzcyQuX2RlZmF1bHQuY29tLmthcmphZ2kuaG9zdDEuYWE6
...
OmFhLg:aa%3A%3Aaa/
...
hhh.test.com/default",
...
"configure_for_dhcp":
...
false,
...
"host":
...
"
...
hhh.test.com",
...
"ipv6addr":
...
"aa::aa"
...
}
], "name": " hhh.test.com",
...
"view":
...
"default"
...
},
...
"object_type":
...
"record:host",
...
"unique_id":
...
"c326fcf8058c4022939050af96a0fdb2"
...
},
...
{ "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDIx:38",
...
"object":
...
{
...
"_ref":
...
"record:host_ipv6addr/ZG5zLmhvc3RfYWRkcmVzcyQuX2RlZmF1bHQuY29tLmthcmphZ2kuaG9zdDEuYWE6
...
OmFhLg:aa%3A%3Aaa/
...
hhh.test.com/default",
...
"configure_for_dhcp":
...
false,
...
"host":
...
"
...
hhh.test.com",
...
"ipv6addr":
...
"aa::aa"
...
},
...
"object_type":
...
"record:host_ipv6addr",
...
"unique_id":
...
"2b19a399c3f747538d879fdd33a4de32"
...
},
...
{ "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDIy:38",
...
"object":
...
{
...
"_ref":
...
"record:host_ipv4addr/ZG5zLmhvc3RfYWRkcmVzcyQuX2RlZmF1bHQuY29tLmthcmphZ2kuaG9zdDEuMS4x
...
LjEuMS4:1.1.1.1/
...
hhh.test.com/default",
...
"configure_for_dhcp":
...
false,
...
"host":
...
"
...
hhh.test.com",
...
"ipv4addr":
...
"1.1.1.1",
...
"mac":
...
"11:11:11:11:11:11"
...
},
...
"object_type":
...
"record:host_ipv4addr",
...
"unique_id":
...
"3fb8fba003d647ceac5796a28459725a"
...
},
...
{ "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDIz:3956302770%3A38",
...
"last_sequence_id":
...
"3956302770:38"
...
}]
- When you update DNS host, host address, and host alias, NIOS updates the sequence IDs of child objects associated with these parent objects even though the changes do not affect the child objects. For example, when you update an existing comment in the host record, NIOS updates the sequence IDs of child objects associated with the respective host record.
...
- .
Example:
curl -k1 -u admin:infoblox -H content-type:application/json
...
-X
...
GET
...
https://10.32.2.202/wapi/v2.5/db_objects?start_sequence_id=2830689052:0\&object_types=
...
record:host,record:host_ipv4addr\;_return_fields=last_sequence_id,object,object_type,o
...
bject.comment\;_return_type=json-pretty
...
The
...
response
...
is
...
as
...
follows:
...
[ { "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDI:27",
...
"object":
...
{
...
"_ref":
...
"record:host/ZG5zLmhvc3QkLl9kZWZhdWx0LmNvbS50ZXN0LmhoaA:hhh.test.com/default",
...
"comment":
...
"hi"
...
},
...
"object_type":
...
"record:host"
...
"unique_id":
...
"1ab6c989d8fd454ca06ffac6ac600fe6"
...
},
...
{ "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDM:27",
...
"object":
...
{
...
"_ref":
...
"record:host_ipv4addr/ZG5zLmhvc3RfYWRkcmVzcyQuX2RlZmF1bHQuY29tLnRlc3QuaGhoLjEuMC4wLjEu
...
:1.0.0.1/hhh.test.com/default",
...
"configure_for_dhcp":
...
false,
...
"host":
...
"hhh.test.com",
...
"ipv4addr":
...
"1.0.0.1"
...
},
...
"object_type":
...
"record:host_ipv4addr"
...
"unique_id":
...
"1ab6c989d8fd454ca06ffac6ac600fe7"
...
},
...
{ "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDQ:2830689052%3A27",
...
"last_sequence_id":
...
"2830689052:27"
...
}
- When an IPv4 or an IPv6 host address changes, NIOS deletes the old record and creates a new record with the updated IP address. Note that new sequence IDs are generated for the associated objects. When you query a host record, NIOS displays the list of host addresses associated with it.
...
Example:
...
curl
...
-k1
...
-u
...
admin:infoblox
...
-H
...
content-type:application/json
...
-X
...
GET
...
https://10.32.2.202/wapi/v2.5/db_objects?start_sequence_id=2830689052:0\&object_types=
...
record:host,record:host_ipv4addr\;_return_fields=last_sequence_id,object,object_type\;
...
_return_type=json-pretty
...
The
...
response
...
is
...
as
...
follows:
...
[ { "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDA:28",
...
"object":
...
{
...
"_ref":
...
"record:host/ZG5zLmhvc3QkLl9kZWZhdWx0LmNvbS50ZXN0LmhoaA:hhh.test.com/default",
...
"ipv4addrs":
...
[
...
{ "_ref":
...
"record:host_ipv4addr/ZG5zLmhvc3RfYWRkcmVzcyQuX2RlZmF1bHQuY29tLnRlc3QuaGhoLjEuMC4wLjIu
...
:1.0.0.2/hhh.test.com/default",
...
"configure_for_dhcp":
...
false,
...
"host":
...
"hhh.test.com",
...
"ipv4addr":
...
"1.0.0.2"
...
} ],
...
"name":
...
"hhh.test.com",
...
"view":
...
"default"
...
},
...
"object_type":
...
"record:host"
...
"unique_id":
...
"1ab6c989d8fd454ca06ffac6ac600fe6"
...
},
...
{ "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDE:28",
...
"object":
...
{ "_ref":
...
"deleted_objects/Li5kZWxldGVkX29iamVjdHMkMA",
...
"object_type":
...
"record:host_ipv4addr",
...
"unique_id":
...
"68cad3406a244aa0b34b3ea3be383598"
...
},
...
"object_type":
...
"deleted_objects"
...
"unique_id":
...
"1ab6c989d8fd454ca06ffac6ac600fe4"
...
},
...
{ "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDI:28",
...
"object":
...
{
...
"_ref":
...
"record:host_ipv4addr/ZG5zLmhvc3RfYWRkcmVzcyQuX2RlZmF1bHQuY29tLnRlc3QuaGhoLjEuMC4wLjIu
...
:1.0.0.2/hhh.test.com/default",
...
"configure_for_dhcp":
...
false,
...
"host":
...
"hhh.test.com",
...
"ipv4addr":
...
"1.0.0.2"
...
},
...
"object_type":
...
"record:host_ipv4addr"
...
"unique_id":
...
"1ab6c989d8fd454ca06ffac6ac600fe9"
...
},
...
{ "_ref":
...
"db_objects/Li5hbGxfY2hhbmdlZF9vYmplY3RzJDM:2830689052%3A28",
...
"last_sequence_id":
...
"2830689052:28"
...
}
- NIOS returns the shared records per zone when you query for them. For example, consider two zones, z1 and z2, and a shared record group, srg1, which contains a shared record sr1. The shared record group srg1 is associated with the zones z1 and z2. Hence, the shared record sr1 is shared between two zones, z1 and z2, but NIOS saves only a single copy of the shared record sr1 in the database. When you query for shared record
...
- record updates, NIOS returns two records for z1 and z2, as sr1 is associated with both the zones, z1 and z2, and saves these records with a UUID and a sequence ID in the table. The response also contains new records with zone pointing to the zone it belongs to, UUID and sequence ID of the new records and a
shared_record_
...
group, which indicates that it is a shared record and not a normal resource record. When you enable Object Change Tracking feature, NIOS clears this table and recreates a new table for the existing shared records.
- Note that NIOS generates two leases in the database when a client sends a DHCP request to the NIOS DHCP server, which is configured with failover association. You can perform either a full or an incremental synchronization in this scenario. Infoblox recommends that you ignore the lease that is generated by the failover DHCP server with
binding_stateasBACKUPand consider the lease withbinding_stateasACTIVE. - File distribution service automatically removes old files from
wapi_outputdirectory if there is no sufficient space for new files. NIOS allocates 50% each of the file distribution area towapi_outputdirectory and normal files. For example, if the file distribution area is allocated 500 MB, then 250 MB is used forwapi_outputdirectory and the remaining 250 MB is used for normal files. - NIOS does not support WAPI paging mechanism. As the synchronization results are displayed in the order of
sequence_id, you mustspecify _max_resultsto achieve paging mechanism for synchronization.
- NIOS deletes all previous scheduled tasks after a restore or an upgrade operation.
...
Note: This operation might take a longer time to complete when you have a large database. For example, 1 million objects on an IB-4010 appliance takes approximately 1 hour. Infoblox recommends that you enable this feature during off-peak hours.
...
.
...
- Maximum number of deleted objects that will be tracked: Specify the total number of deleted objects that must be present in the database. The minimum value is 2,000 and the maximum value is 20,000. The default value is 4,000.
3. Save the configuration.
| Anchor | ||||
|---|---|---|---|---|
|
| Anchor | ||||
|---|---|---|---|---|
|
...
- When _output_location = "FILE_DISTRIBUTION"
...
When you set the output location as mentioned above, you must specify a file name or a prefix for the file. NIOS saves the output file in the file distribution area and displays an error message if you do not specify a file name or a prefix. For more information about file distribution area, see Managing Directories.
When you select the above output location for a Grid Master Candidate, you must select Allow Upload to Grid Members to upload files to the file distribution area. Infoblox recommends that you use the Grid Master Candidate to offload the Grid Master. You must enable a full synchronization during off-peak hours if protocol services are running on the Grid Master Candidate. For more information, see Enabling Upload to Grid Members.
Example:
curl -k1 -u admin:infoblox -X POST 'https://..../wapi/v2.5/fileop?_function=read' -H 'Content-Type: application/json; charset=UTF-8' -d '{"_filename": "test.json", "_output_location":"FILE_DISTRIBUTION","_object": "db_objects", "all_object_types_supported_in_version": "2.5","_encoding": "ROWJSON"}'
You can specify either _object = db_objects or all_object_types_supported_in_version=2.5 to retrieve all objects. When you specify _object = db_objects, NIOS returns only standard Restful API fields as response. To retrieve all fields of all objects, you can specify all_object_types_supported_in_version=2.5. To fetch the output file, start file distribution service and use the following URL:
curl -k1 -u admin:infoblox -X GET http://<ipaddress>/wapi_output/test.json -H 'Content-Type:application/json'
...