Fortinet black logo
7.2.0

Requirements

Requirements

  • Virtual appliance settings will vary depending on the underlying hardware being used for the hosting server. The ideal result is to yield a virtual environment where the average load does not exceed the Total GHz Rating of CPU Resources Allocated.

    • Determine the appropriate parameters for the virtual environment. It is recommended they be comparable to those of hardware-based FortiNAC appliances. Refer to the following tables in the FortiNAC Data Sheet:

      • Hardware Server Sizing - Hardware server part number most appropriate for the target environment

      • Specifications - Details regarding the applicable part number

      • VM Server Resource Sizing - Suggested values for memory and CPU to allocate for the virtual appliance

  • KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V).

  • KVM is open source software. The kernel component of KVM is included in mainline Linux, as of 2.6.20.

    Note: It is beyond the scope of this document to cover specific KVM environments and tools. Please refer to the specific system administration documentation for the KVM environment being used and any GUI interface, Web UI, Virtual Manager or command line tools available.

  • Open Ports: The number of open (listening) TCP/UDP ports configured by default on the FortiNAC appliance is based on current best practices. These ports are kept to a minimum to provide maximum security by explicitly restricting unnecessary access from the outside. The best practice is to keep the number of open ports to a minimum, and block all other ports. If you need to provide users access to network resources through a static port (e.g., from outside a firewall), the best option is to allow users to connect by VPN. Refer to section Open Port List of the FortiNAC Deployment Guide in the Fortinet Document Library.

Requirements

  • Virtual appliance settings will vary depending on the underlying hardware being used for the hosting server. The ideal result is to yield a virtual environment where the average load does not exceed the Total GHz Rating of CPU Resources Allocated.

    • Determine the appropriate parameters for the virtual environment. It is recommended they be comparable to those of hardware-based FortiNAC appliances. Refer to the following tables in the FortiNAC Data Sheet:

      • Hardware Server Sizing - Hardware server part number most appropriate for the target environment

      • Specifications - Details regarding the applicable part number

      • VM Server Resource Sizing - Suggested values for memory and CPU to allocate for the virtual appliance

  • KVM (for Kernel-based Virtual Machine) is a full virtualization solution for Linux on x86 hardware containing virtualization extensions (Intel VT or AMD-V).

  • KVM is open source software. The kernel component of KVM is included in mainline Linux, as of 2.6.20.

    Note: It is beyond the scope of this document to cover specific KVM environments and tools. Please refer to the specific system administration documentation for the KVM environment being used and any GUI interface, Web UI, Virtual Manager or command line tools available.

  • Open Ports: The number of open (listening) TCP/UDP ports configured by default on the FortiNAC appliance is based on current best practices. These ports are kept to a minimum to provide maximum security by explicitly restricting unnecessary access from the outside. The best practice is to keep the number of open ports to a minimum, and block all other ports. If you need to provide users access to network resources through a static port (e.g., from outside a firewall), the best option is to allow users to connect by VPN. Refer to section Open Port List of the FortiNAC Deployment Guide in the Fortinet Document Library.