Differences

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

--- infoblox_nios:deploy_nios_vm [2024/08/14 03:57] – bstafford
+++ infoblox_nios:deploy_nios_vm [2025/08/07 16:48] (current) – [VMware] bstafford
@@ Line 1: / Line 1: @@
 ====== Deploy Virtual Infoblox Appliance ======
-Where possible, deploy all vCPU on same socket. Specifically, if you require more vCPU than you have per physical socket, it is possible that NUMA might cause performance to be sub-optimal.
+Where possible, deploy all vCPU on same socket. Specifically, if you require more vCPU than you have per physical socket, it is possible that NUMA might cause performance to be sub-optimal. Specifically, it may cause issues if you are using ADP or DCA. If you are not using ADP or DCA, NUMA=1 is not needed as much.
+The resizable VM can scale up to 2.5TB disk.
 ===== Documentation =====
   * [[https://docs.infoblox.com/space/NVIG/35786250/About+Infoblox+NIOS+Virtual+Appliance+for+VMware|Vmware]]
@@ Line 18: / Line 22: @@
 The following steps show how to deploy an Infoblox VMware OVA image onto VMware Workstation on Windows 10. Deploying on ESXi should be similar.
-  - Deploy nios-8.4.3-ddi.ova by double clicking it in Windows Explorer.
+  - Deploy nios-9.0.7-ddi.ova by double clicking it in Windows Explorer.
   - Accept the terms of the license agreement and click 'Next'.
   - Pick a name for the VM and click 'Next'.
   - Select the model of Infoblox Appliance you want to deploy (e.g. TE-815 or TE-825, etc). This is how VMware knows how much RAM and CPU to set on the VM.
   - You now have an option to pre-populate configuration but ignore this and just click 'Import'.
-  - The machine will deploy and boot. Make sure you update the VM's four network interfaces to be connected to the appropriate VLAN in the hypervisor. Also remember that LAN1 (the interface you access by default) is the second network interface. The first interface is the management interface but that is not used by default. Also remember that, **IN A LAB**, you get away with reducing the RAM from 16GB to 4Gb (or even 2GB) and from 4CPU to 2CPU (or even 1CPU). (Order of network interfaces is MGMT, LAN1, HA, LAN2)
+  - The machine will deploy and boot. Make sure you update the VM's four network interfaces to be connected to the appropriate VLAN in the hypervisor. Also remember that LAN1 (the interface you access by default) is the second network interface. The first interface is the management interface but that is not used by default. Also remember that, **IN A LAB**, you get away with reducing the RAM from 16GB to 4Gb (or even 2GB) and from 4CPU to 2CPU (or even 1CPU). (Order of network interfaces is MGMT, LAN1, HA, LAN2). **HOWEVER**, I've seen cases where you need 8GB because giving the VM less means that it won't connect to the Infoblox Portal.
   - Log into the VM with the username ''admin'' and the password ''infoblox''.
   - Run the ''set temp_license'' command so that we can set temporary 60 day licences. This bit can be skipped if you have actual licences but it is useful in a lab environment.
@@ Line 35: / Line 39: @@
 **Remember**, when deploying VM HA in VMware, you need to update the security settings on the port-group that is used by the Infoblox VM's to accept "MAC address changes" and "Forged transmits". This is so that VMware allows the VM's to have multiple MAC addresses per vNIC (which is needed for Infoblox HA). [[https://www.edge-cloud.net/2013/05/21/infoblox-vnios-ha-pair-vip-unreachable-when-deployed-on-vsphere|More data here]].
+**Remember** You can specify temp licences with
+<code>enterprise grid dns dhcp rpz cloud_api vnios nios cloud IB-V926</code>
 ===== MGMT Port =====