An administrator can add equipment to DCImanager regardless of its geographical location and data centers. Remote equipment can be grouped according to its location. To do so, you can utilize locations in the platform. 

A location is an interface that allows DCImanager to manage equipment from one data center. Every location in the data center has a special server that is used as a DHCP server and storage of OS templates for all servers in the location. A server must be physical or virtual based on KVM virtualization. To distribute the load evenly, it is recommended to use separate servers for platform and location. Learn more in the article Adding a location


  • Supported OS:
    • AlmaLinux 8;
    • CentOS 7;
    • Ubuntu 20.04.
      The OS on the location server may not match the OS of the parent server;
  • Servers-locations must have sufficient disk space for OS templates. We recommend allocating at least 100 Gb;
  • Servers-locations must have at least 8 Gb RAM;
  • Server-location and equipment in the location must be in the same L2 network segment;
  • Server with the platform must have access to servers-locations via SSH;
  • Applications using DHCP, TFTP, and HTTP must not be installed on servers-locations;
  • Firewall other than firewalld must not be used on servers-locations.
  • In the L2 segment of the location network the STP protocol should not be used.

Port settings

For the location, the following ports are used:

  1.   DCImanager access to location:
  2.   Servers access to location:
    • 67/UDP — to enable DHCP;
    • 69/TCP — to enable TFTP;
    • 111, 2049, 32767/TCP — to enable NFS;
    • 445/TCP — to enable Samba;
    • 1500/TCP — to enable Nginx web server.