infoblox:deploy_vm
This is an old revision of the document!
Deploy Virtual Infoblox Appliance
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.
- 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 rom 4CPU to 2CPU (or even 1CPU).
- Log into the VM with the username
adminand the passwordinfoblox. - Run the
set temp_licensecommand 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. - Select option 2 for “DNSone with Grid (DNS, DHCP, Grid)”. This will restart the web UI and return you to the CLI
- Run the
set temp_licensecommand again. - Select option 4 for “Add NIOS License” and then select the apporpriate VM licence (e.g. option 3 for VIB-815 model)
- You will then be returned to the CLI. At this point you need to wait about 30 seconds and then the VM will restart.
- Run the
set networkcommand to configuration the LAN1 interface IP / subnet and default gateway. (Probably) don't bother with IPv6 and do not become a Grid Member. This will restart the appliance. - You can now access the Web UI by accessing the IP you set. You will not be able to SSH in unless you enable remote console access.
infoblox/deploy_vm.1601031124.txt.gz · Last modified: (external edit)
