Prerequisites

Proxmox Deployment

The DataCore Installation Manager for Proxmox requires proper name resolution for both the Proxmox hosts and the virtual machines being deployed.

Before starting deployment, ensure that the DNS or the HOSTS file on the deployment machine is updated so that the Proxmox host resolves to the same IP address using both its hostname (NETBIOS name) and fully qualified domain name (FQDN).

Proxmox Hosts (Two or More Hosts)

  • Proxmox hosts must be joined in a cluster.
  • Each host should have one or more unpartitioned physical disks. This prerequisite is required only if the option “Automatically create pool” is selected in the DataCore Installation Manager for Proxmox > DataCore Proxmox Virtual Machine Settings section.
  • During the initial SANsymphony deployment, SANsymphony will be available in trial mode. The total disk capacity should not exceed 1 PiB during this time.
  • At least 15 GiB of free storage space must be available on each Proxmox server to upload the ISOs.
  • Each host should have two public NICs:
    • One for the DataCore Installation Manager for Proxmox to connect to the hosts
    • One for Cluster management as per the best practices guide in Proxmox.
  • Each host must have the following packages installed:
    • jq and multipath (Example: apt install jq multipath).
  • SSH connections must be allowed in the firewall from the machine where the DataCore Installation Manager for Proxmox is running.

DataCore Server Virtual Machine

The DataCore Installation Manager for Proxmox must be able to connect to all Proxmox hosts.

Firewall Settings

You can either enable individual rules or specific port ranges to configure the firewall settings.

  • Outbound Rules
    • Windows Management Instrumentation (WMI-Out): Any port for svchost.exe
  • Inbound Rules
    • Windows Management Instrumentation (WMI-In): Any port for svchost.exe
    • Windows Management Instrumentation (ASync-In): Any port for unsecapp.exe
    • Windows Management Instrumentation (DCOM-In): Local port is 135
    • Remote Volume Management (RPC-EPMAP): RPC Endpoint Mapper is 135
    • Remote Volume Management – Virtual Disk Service (RPC): RPC Dynamic Port range is 49152-65535 by default
    • Remote Volume Management – Virtual Disk Service Loader (RPC): RPC Dynamic Port range is 49152-65535 by default
    • File and Printer Sharing (Echo Request – ICMPv4-In): Any port for ICMP protocol

Ports

Ensure the following local ports are open for incoming connections (assuming default configuration of Dynamic RPC ports):

  • 135 TCP (WMI/RPC)
  • 137-139 TCP/UDP (File Sharing)
  • 445 TCP (File Sharing/TCP)
  • 49152-65535 TCP (RPC)
  • All ports for ICMP (ping)