Differences

This shows you the differences between two versions of the page.

--- infoblox_nios:licenses [2023/03/05 08:58] – bstafford
+++ infoblox_nios:licenses [2025/07/30 15:28] (current) – [License a NIOS VM] bstafford
@@ Line 1: / Line 1: @@
 ====== Infoblox Licenses ======
-Note that B1TD Essentials is licenced per member. If the member is a HA pair of two nodes, you only need one licence and another license for $0 will be issued.
+Note that B1TD Essentials is licenced per member. If the member is a HA pair of two nodes, you only need one licence and another license for $0 will be issued. (IB-SUB-THREAT-ESNTL-HA)
+When you use the "set licence" command, you must to so on the CLI of the actual member that you are installing he license on (i.e. you can't use the GM CLI for all licenses)
+The DNSFW/RPZ license (IB-SWTL-DFW-TE-xxxx) is sold per node. In a HA-Pair, you will need two DNSFW licenses - one per HA-Pair member.
 For expiry details [[https://docs.infoblox.com/space/nios86/25593433/License+Expiry|here]] and [[https://support.infoblox.com/s/article/10989|here]], between 8.0 and 8.2, the subscription behaviour didn't work as it does today. 8.3.6+ to 8.4 and all beyond, this was fixed. Changed to DNS and DHCP after subscription expiry should work.
+===== X6 ======
+  * When you purchase X6 with Microsoft Management installed, be aware that you can't install Microsoft Management on a NIOS VM that has the CP licence installed. So, although the X6 appliance is licenced for CP, you can't install it if you want to use Microsoft Management.
+  * You need to install DNS first before installing RPZ and DTC. If you try to install all licences at the same time, it is possible that RPZ and DTC will not install and you just have to re-import those licences and they will install.
+===== Temp Licenses =====
+Be aware, unlike [[https://docs.infoblox.com/space/nios90/280667194/Managing+Licenses+in+NIOS+9.0.0#NIOS-Licenses-and-License-Expiry|production NIOS licences]], if you set a temp licence on NIOS, when the licence expires, the services are no longer reliable. If you boot a NIOS VM that has its licence expired, the services will not start.
+If the VM is already running, if the service stops, it won't start. If the service is kept running, certain actions will not work (zone updates, etc).
+IPAM is still usable manually.
 ===== Setting NIOS Licences =====
@@ Line 17: / Line 30: @@
   * Add Multi-Grid Management license
   * Add Query Redirection license
+  * Add Threat Protection (Software add-on) license  (causes a system restart)
+  * Add Threat Protection Update license
   * Add Response Policy Zones license
   * Add FireEye license
@@ Line 22: / Line 37: @@
   * Add Cloud Network Automation license
   * Add Security Ecosystem license
+  * Add Threat Analytics license
   * Add Flex Grid Activation license
   * Add Flex Grid Activation for Managed Services license
@@ Line 30: / Line 46: @@
   * Add Reporting subscription license
-This ist list list of NIOS Licenses you can add
+This list list list of NIOS Licenses you can add
   * IB-V805
   * CP-V805
@@ Line 47: / Line 63: @@
   * IB-V5005 (Reporting Server)
+For VMware temp licencing at deployment
+  * dns=dns
+  * dhcp=dhcp
+  * enterprise=grid
+  * nios=appliance
+===== ADP =====
+See the dedicated [[infoblox_nios:adp|ADP page]] for more details.
 ===== NIOS License Renewal =====
 When a license is renewed, the support portal is automatically updated. However, for NIOS appliances you will need to redownload the appliance licence key and install it via the Grid Master GUI.
+When you apply a renewal license, services are not impacted. Tested with DNS and DHCP services.
 ===== License a NIOS VM =====
@@ Line 59: / Line 86: @@
   - Log into the Infoblox Support Portal - https://support.infoblox.com/
   - Click "My Products" on the menu at the top of the page.
-  - Go to "Subscriptions" and you should see the list of licences purchased. If you are a distributer, you may have to "Filter Customer" at the top of the screen. Verify that the number of subscriptions matches what you are expecting.
+  - Click "Create VM/Grid and Assign Software" blue button on the left.
-  - Go to "Hosts" and you should see that Infoblox have helpfully pre-populated entries for the new VMs with random serial numbers and SKU of "IB-VM".
+  - Select the correct End Customer.
-  - Click "Create Virtual Host".
   - Paste the Hardware ID into the field "Virtual Host Hardware ID".
-  - Set License Technology to "DDI"
+  - Set License Technology to "DDI (for NIOS and BloxOne)"
+  - Do **NOT** click "Is Grid Wide?" unless you are creating a VM instance to represent "Grid Wide" licences (e.g. for reporting).
   - Click "Save & Assign Software". This will take you to the screen to assign software to this VM. It will start off by saying "There is no Software assigned to this Host". Further down the screen you can see a list of "Software available to be assigned to Host". Take a note of "Total Quantity" and "Available Quantity".
   - What I do at this stage is find the entry for the NIOS licence (e.g. "IB-SWTL-BASE-NIOS-825"). Click the + symbol to add this license and you should find that the other licences for the VM get added automatically (e.g. IB-SWLT-GD and IB-SWTL-NS1).
@@ Line 80: / Line 107: @@
   * You can create new zones but they can't be queried.
   * If you restart the appliance, the DNS server stops functioning.
+In theory the above is true. Also in theory, when a "TRIAL" subscription expires, the functionality stops completly.
 ===== Set NIOS Grid Wide Licence =====
 When you set a Grid Wide License, you must create a VM in the support portal using the Grid UUID.
+**NOTE**: You need to already have a Grid licence and NIOS licence installed. Set a temp licence if required.
 <code>show license_uid</code>
+===== Pool Licenses =====
+Pool licenses are supported but there are some [[https://support.infoblox.com/s/article/Limitations-of-pool-licenses-in-NIOS|caveats]] in the 8.6+ code.
+The following are the limitations of using pool licenses in NIOS:
+  * When a pool license has expired, you cannot manually delete the license.
+  * If you replace an expired pool license with a replacement license, the new license is installed and the expired license is left as is.  This does not impact the functionality but is not good user experience.
+  * Pool licenses can only be removed by installing a new license file. Any of the pool licenses present in the Grid but not present in the license file will be removed. The only way to remove a pool license is to apply a "new" pool license which in turn will remove any of the current licenses that are not contained within the "new" pool license.
+A (limited) workaround for these limitations is to install a static license. A static license installed on a Grid member will take precedence over the pool license. Dynamic licenses are released from the associated Grid member and returned to the corresponding pool when a valid static license is applied to the same feature on the Grid member.