An administrator can add equipment to DCImanager 6 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 6 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 Location management. 

Requirements

  • Supported OS:
    • AlmaLinux 8;
    • Ubuntu 20.04.
      The OS on the location server may not match the OS of the parent server;

      CentOS 7 operating system:

      • not supported for new product installations;
      • for existing product installations is supported until EOL on June 30, 2024.
  • 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.

  • Server-location must be able to download:

    • OS packages for configuring the location (e.g. docker, docker-compose, etc.);

    • docker images for location updates from the ISPsystem registry — docker-registry.ispsystem.com;

    • OS images from the ISPsystem repository — download.ispsystem.com;

    • ISO images from external resources.

/etc/hosts file

Make sure that the /etc/hosts file has an entry for the server in the format:

<server IP address> <server hostname>
CODE

/etc/resolv.conf file

Make sure that the /etc/resolv.conf file has entries in the format:

nameserver <IP address of the DNS server>
CODE

If the IP address of the systemd-resolved local service (127.0.0.53) is specified as the DNS server, check that the DNS server addresses are specified in /etc/systemd/resolved.conf:

DNS=<servers list>
CODE

Port settings

For the location, the following ports are used:

  • DCImanager 6 access to location:
  •  servers access to location:
    • 67/UDP, 68/UDP — to enable DHCP;
    • 69/UDP — to enable TFTP;
    • 111/TCP, 2049/TCP, 32767/TCP, 111/UDP, 2049/UDP, 32767/UDP — to enable NFS;
    • 445/TCP — to enable Samba;
    • 1500/TCP — to enable Nginx web server;
    • NetFlow statistics collection ports. Default values:
      • 2056/UDP — NetFlow v5;
      • 2055/UDP — NetFlow v9,
      • 6343/UDP — sFlow;

  • outgoing connections to the equipment:

    • servers:

      • IPMI — 623/TCP, 623/UDP;

      • Redfish — 443/TCP;

      • BMC web interface — 80/TCP, 443/TCP;

    • switches:

      • eAPI — 80/TCP, 443/TCP;

      • SNMP — 161/UDP, 162/UDP;

      • NX-API — depends on the switch settings. Default value is 8181/TCP;

      • NetConf — 22/TCP, 830/TCP;

      • RouterOS API — depends on the switch settings. Default value is 8728/TCP, 8729/TCP;

    • PDU:

      • SNMP — 161/UDP, 162/UDP;

    • UPS:

      • SNMP — 161/UDP, 162/UDP.

Useful tips

Related topics:

Knowledge base articles: