---
title: "Known Limitations"
canonical: "https://docs.infoblox.com/space/vniosopstack/1096908948/Known%20Limitations"
format: markdown
---
vNIOS for OpenStack and vNIOS for Red Hat OpenStack supports most of the features of the Infoblox NIOS appliances with the following limitations:

- 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 KVM may violate the terms of the vNIOS licensing and support models. The vNIOS appliance may not join the Grid or function properly.
- If the vNIOS instance fails to launch, the ports created for the instance are not deleted automatically. You need to delete them manually.
- When you start an FTP connection on OpenStack with the **Listen** **on** **port** field set it to 20 and 21, you need to manually add a rule to allow the 20 and 21 ports. This ensures that the connection is successful.
- Connection to the FTP service might fail when the virtual appliance enters the passive mode. To avoid this, do the following:
  - Use active mode instead of passive mode.
  - Modify the vnios-sec-group security group to open ports 1023 and above.
  - Use the FTP client inside the internal network.
- The vNIOS instances deployed in the OpenStack environment do not support HSM Safenet groups.
- At certain times, a power failure (or an unexpected reboot) of the VM host may cause corruption of the VM guest unless writes are correctly persisted by setting the value of the `disk_cachemodes` parameter to `writethrough`. For more information, see the *[Deploying vNIOS for OpenStack](https://infoblox-docs.atlassian.net/wiki/spaces/vniosopstack/pages/1097400363)* topic.
- High Availability:
  - You cannot configure the reporting virtual appliance as an HA pair. You also cannot configure it as a Grid Master or Grid Master Candidate. You can use it only as a dedicated reporting server in the Grid.
  - In an HA environment, if a NIC interface is configured as DPDK (instead of DIRECT), ensure that the port's security is disabled for a successful operation.