This topic lists the limitations on each vNIOS appliance:

vNIOS for VMWare Limitations

The Infoblox vNIOS for VMware can also run on Cisco SRE-V (Services Ready Engine Virtualization), which is part of the Cisco UCS (Unified Computing System) Express. For more information about vNIOS for VMware, refer to the Infoblox Installation Guide for vNIOS Software on VMware.
vNIOS for VMware appliances support most of the features of the Infoblox NIOS appliances, with the following limitations:

• You must have a vNIOS license installed on the appliance before you can access the Infoblox GUI.
• vNIOS appliances do not support the following features:
  • Configuration of port settings for MGMT, LAN, LAN2, and HA ports
  • The bloxTools environment
• The IB-BOB virtual appliance is supported on Cisco SRE-V and can function as a Grid member only. It does not support configuration as an independent appliance, an HA pair, a Grid Master, or a Grid Master candidate. It also does not support access to the Infoblox GUI.
• The IB-VM-250 virtual appliance supports all the services provided by vNIOS virtual appliances, but it is not recommended as a Grid Master or Grid Master candidate.
• When you configure an HA pair, both nodes in the HA pair must be vNIOS instances. You cannot configure a physical NIOS appliance and a vNIOS instance in an HA pair.
• vNIOS appliances run on virtual hardware. They do not have sensors to monitor the physical CPU temperature, fan speed, and system temperature.
• Changing the vNIOS appliance settings through the VMware vSphere or vCenter console may violate the terms of the vNIOS licensing and support models. The vNIOS appliance may not join the Grid or function properly.

vNIOS for Riverbed Limitations

vNIOS appliances on Riverbed have the following limitations:

• They can function as Grid members only. You cannot configure them as HA (high availability) pairs, Grid Masters, Grid Master candidates, or independent appliances.
• On a Grid with a vNIOS appliance on Riverbed as a Grid member, the maximum storage space for HTTP, FTP and TFTP is 1 GB (a Grid with only Infoblox appliances provides a maximum of 5 GB for these services), core files are 100 MB each, and syslog and inflobox.log files are 20 MB each. Scheduled backup file is 100 MB.
• The LAN interface is the only network interface available on the vNIOS appliance. You cannot configure the speed and transmission type (full or half duplex) of the network interface.
• You can use the traffic capture tool of the vNIOS software package to capture traffic only on the LAN port of the vNIOS appliance.
• vNIOS appliances on Riverbed do not support the following features:
  • Anycast addressing
  • Configuration as a DHCP lease history logging member
  • Dedicated MGMT port
  • NTP service
  • bloxTools environment
  • Configuration for managing Microsoft® Windows DNS servers

vNIOS for Hyper-V Limitations

vNIOS for Microsoft Windows 2008 R2 and 2012 R2 server appliances support most of the features of the Infoblox NIOS appliances, with the following limitations:

• You must have a vNIOS license installed on the appliance before you can access the Infoblox GUI.
• vNIOS appliances do not support the following features:
  • Configuration of port settings for MGMT, LAN, LAN2, and HA ports
  • The bloxTools environment
• All the IB-VM appliance models support all the services provided by vNIOS virtual appliances, but Grid Master or Grid Master Candidate is not supported.
• The Captive Portal is supported only on IB-VM-1410 virtual appliances.
• vNIOS appliances run on virtual hardware. They do not have sensors to monitor the physical CPU temperature, fan speed, and system temperature.
• Changing the vNIOS appliance settings through the Hyper-V Manager or Virtual Machine Manager Administrator console may violate the terms of the vNIOS licensing and support models. The vNIOS appliance may not join the Grid or function properly.

vNIOS for Xen

vNIOS virtual appliance for Xen supports most of the features of the Infoblox NIOS appliances, with the following limitations:

• vNIOS appliances do not support the following features:
  • Configuration of port settings for MGMT, LAN, LAN2, and HA ports
  • The bloxTools environment
• When you configure an HA pair, both nodes in the HA pair must be vNIOS instances. You cannot configure a physical NIOS appliance and a vNIOS instance in an HA pair.
• vNIOS appliances run on virtual hardware. They do not have sensors to monitor the physical CPU temperature, fan speed, and system temperature.
• Changing the vNIOS appliance settings through the vNIOS for Xen virtual appliance console may violate the terms of the vNIOS licensing and support models. The vNIOS appliance may not join the Grid or function properly.