DCImanager 6
Documentation
/
DCImanager 6
/
Locations
/
Locations. General information

Locations. General information

You can connect equipment from several data centers to DCImanager 6 regardless of their remoteness. Locations are used to group equipment from one data center.

In the documentation, the word “location” is used in two meanings:

The interface through which DCImanager 6 manages equipment from a single data center.

  1. A server that simultaneously:
    • serves as a DHCP server and operating system (OS) template repository for all servers in the data center;
    • provides the platform with access to the data center equipment.
  2. 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

  • The location server must be physical or virtual based on KVM virtualization;
  • The location server must run on Ubuntu 24.04.
    CentOS 7 OS is not supported. If CentOS 7 is installed on the server, you can migrate to a supported OS: Migrating from CentOS 7.
  • Location servers must have sufficient disk space for OS templates. We recommend allocating at least 100 Gb;
  • Location servers must have at least 8 Gb RAM;
  • Location servers and equipment in the location must be in the same L2 network segment;
  • Server with the platform must have access to location servers via SSH;
  • Applications using DHCP, TFTP, and HTTP must not be installed on location servers;
  • 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.

  • Location servers 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>

/etc/resolv.conf file

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

nameserver <IP address of the DNS server>

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>

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.

Preparing to set up a location with Ubuntu OS

To prepare to set up a location with Ubuntu OS, update the system:

  1. Connect to the location via SSH.

  2. Run the following commands:

    apt update
    apt upgrade