Before joining a member to the Grid, you can first enable provisional licenses and make necessary configurations on the offline member, which allows DNS and DHCP data to be associated with the member prior to its deployment. Note that pre-provisioned members are treated as offline members. There are a few guidelines to consider before you pre-provision a member. For more information about the guidelines, see Guidelines for Pre-provisioning Offline Grid.
When you add a new member to the Grid, the Pre-Provisioning tab is displayed in the Grid Member Properties editor. You can pre-provision the member by defining its hardware model and enable certain provisional licenses through the Pre-Provisioning tab. This tab is not displayed after the member successfully joins the Grid. NIOS supports the following provisional licenses: Cloud Platform, DHCP, DNS, DNS Traffic Control, Enterprise (formerly Grid), FireEye, Microsoft Management, RPZ (Response Policy Zone), and vNIOS. You must enable provisional licenses before you can make supported configurations on the pre-provisioned member. For more information about these licenses, see the About Provisional Licenses section.

Note

You must have the Enterprise and vNIOS licenses pre-provisioned in order for a vNIOS appliance to join the Grid. For a cloud virtual appliance, include the Cloud Platform license.

To pre-provision an offline Grid member and join it to the Grid at a later time, complete the following:

Add a new single member or HA member to the Grid, as described in Adding a Single Member or Adding an HA Member.
Pre-provision the offline member, as described in the Configuring Pre-Provisioned Members section.
Configure services to use the pre-provisioned member.
Obtain permanent licenses you have specified for pre-provisioning and use the set license CLI command to install the licenses on the member. For more information about CLI commands, refer to the Infoblox CLI Guide.
Join the pre-provisioned member to the Grid, as described in Joining Appliances to the Grid. For guidelines about joining pre-provisioned members, see Guidelines for joining Pre-Provisioned Members.

Guidelines for Pre-provisioning Offline Grid Members

Before you pre-provision a Grid member, consider the following:

A pre-provisioned Grid member is an offline member. When you upgrade a Grid that has a pre-provisioned member, the upgrade behaves the same way as it does when you upgrade the Grid that has an offline member. Note that you cannot pre-provision a member or update its settings during a scheduled upgrade. For more information about upgrades, see Upgrading NIOS.
You cannot change the pre-provisioned member configuration after you save it. To change the configuration, you must first delete the member and pre-provision it again. If you want to delete certain provisional licenses or change the hardware model for the pre-provisioned member, you must also first delete the existing member and define a new one. For information about deleting a member, see Removing a Grid Member.
When you assign a network, zone, or IPv4 DHCP failover association to a pre-provisioned member, the Restart Service button is not displayed. If you restart any service on a pre-provisioned member, no action is actually taken even though you may receive a message indicating that the operation may take a few minutes. When you join the member to the Grid, NIOS will run respective member services on the joined member. For more information about service restarts, see Restarting Services.
NIOS allows you to backup information about the pre-provisioned member. When you perform a forced restore however, NIOS does not restore the pre-provisioned licenses if you have already installed permanent NIOS licenses on the corresponding member. For more information about backup and restore, see Backing Up and Restoring Configuration Files.
You can use Manage Member Services to manage the pre-provisioned member services. For more information, see Monitoring Member Services.

Configuring Pre-Provisioned Members

The pre-provisioning feature is disabled by default. You must select a supported hardware model for the member to enable this feature.
To pre-provision an offline member, login to the Grid Master and complete the following:

From the Grid tab, select the Grid Manager tab -> Members tab, and then click the Add icon.
In the Add Grid Member wizard, add a new member as described in Adding a Single Member.
After you add the member to the Grid, select the member in the Members tab and click the Edit icon.
In the Grid Member Properties editor, select the Pre-Provisioning tab, and complete the following:
- Member Type: Displays the member type that you have selected in the General tab. The pre-provisioning feature is supported only for Infoblox and Virtual NIOS member types. Note that you must select a hardware model for the member in order to enable the pre-provisioning feature.
- Hardware Model: Select the hardware model from the drop-down list. Grid Manager displays only the supported hardware models for the specified member type. Once you select the hardware model, the pre-provisioning feature is enabled for the member. NIOS allows you to pre-provision HA members that have the same or different hardware models for Node 1 and Node 2. A few hardware specific features, such as DSCP, VLAN, LAN2, and LOM (Light Out Management), are enabled based on the pre-provisioned hardware model you specify here.
- Provisional Licenses: Select the licenses that you want to enable for the pre-provisioned member. You can select the licenses only after you have specified the hardware model for the member. Once you select and enable a license, you can no longer modify the hardware model for the member. Note that the permanent licenses that you later add to the member must include the ones that are specified for pre-provisioning.
Save the configuration.
Note that after you save the configuration, you can no longer modify the hardware model for the member. You also cannot disable any provisional licenses, though you can add new ones. To disable provisional licenses, you must first remove the pre-provisioned member and then configure a new one.

About Provisional Licenses

If a member has never joined a Grid, you can pre-provision this member provided that you define the hardware model for the member and assign provisional licenses to it. Provisional licenses are not permanent NIOS licenses. Though they do not have expiration dates or validity periods, you must replace these licenses with corresponding permanent licenses before you join the member to the Grid.

Note

Before you join the member to the Grid, use the CLI command set license to add corresponding permanent licenses that you have specified for pre-provisioning. For information about CLI commands, refer to the Infoblox CLI Guide{_}. You can also allocate pre-purchased licenses from the pool. For information, see You can use the following OpenStack cloud-init template to configure an IB-V815 as a Grid Master

NIOS supports the following provisional licenses: Cloud Platform, DHCP, DNS, DNS Traffic Control, Enterprise (formerly Grid), FireEye, Microsoft Management, RPZ (Response Policy Zone), and vNIOS.

After you configure the offline member, you can select the pre-provisioned member from the corresponding wizards and editors based on the required license(s). The following table lists the wizards and editors from which you can select a pre-provisioned member when required pre-provisioned licenses are enabled:

Wizards and editors from which you can select a pre-provisioned member	Required license(s)
DNS Zones and Name Server Groups	dns
DHCP IPv4 and IPv6 networks	dhcp
IPv4 DHCP Failover Association	dhcp
Microsoft servers Note that the initial synchronization with Microsoft servers is read-only. When you join the appliance to the Grid, the appliance removes all Microsoft management objects that you have configured on the Microsoft servers after the synchronization. The configuration on the Microsoft servers will replace the configuration on the NIOS appliance.	ms_management
Grid Members	vnios
Grid license	enterprise
Response Policy Zones	RPZ
Response Policy Zones	FireEye
DNS Traffic Control	DTC
Cloud tabs and related wizards and editors	cloud_api

Note

If you configure a DHCP Failover using an online member and a pre-provisioned member, assign it to a range, and start DHCP service, no addresses will be served because the initial synchronization does not happen due to the pre-provisioned offline member. NIOS logs the following message in the syslog: 2013-12-24T08:37:23+00:00 daemon (none) dhcpd[8790]: info DHCPDISCOVER from cb:86:a8:45:6c:5c via 10.120.21.236: not responding (recovering)

Guidelines for Joining Pre-Provisioned Members to the Grid

Before you join a pre-provisioned member to the Grid, ensure that you verify the appliance model and provisional licenses for the member. For information about how to join a member to the Grid, see Joining Appliances to the Grid.
Note the following about joining a pre-provisioned member to the Grid:

If you install fewer permanent licenses than the specified provisional licenses, you cannot join the member to the Grid.
If the pre-provisioned member does not have any provisional licenses enabled, you can join the member to the Grid provided that you install a permanent Grid license on the member.
You must install at least the set of permanent licenses that were specified for pre-provisioning along with any other needed licenses, except for the following:
- You can join the member to the Grid if the pre-provisioned member is a vNIOS virtual appliance and has only the DNS license enabled, and you install both the vNIOS and DNS licenses on the member.
- Similarly, you can join the member to the Grid if the pre-provisioned member is a vNIOS virtual appliance and has both DNS and DHCP licenses enabled, and you install the vNIOS, DNS, and DHCP licenses on the member.
After you successfully join the pre-provisioned member to the Grid, provisional licenses are removed and permanent licenses take effect.
After the member joins the Grid successfully, the Pre-Provisioning tab is not displayed in the Grid Member Properties editor.

Browser not supported