Minimum Requirements

  • Five Virtual Machines. 
    • Ensure that these dedicated virtual machines have unique hostnames with no other production applications running on them. Install and update base OS packages to the latest versions.
    • Requires an active internet connection to automatically install and configure software dependencies.
    • Does not have any pre-existing OS level firewall rules (iptables).
  • vCPU/Core: 8 for each node
    • Example: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50 GHz
  • RAM: 32 GB for each node
  • Load balancer or network configuration (DNS) to provide a single network endpoint for the cluster.
  • NIC Interface: 2
Note

This is the minimum recommendation for initial installation. Monitor your network environment and add additional CPU, RAM, and Disk space, as required.


Network Port Requirements

Open the following ports for a successful HA 
Unable to show "metadata-from": No such page "_space_variables" installation:

  • 80, 443 for HTTP/HTTPS
    Inbound ( Edgeview access and initial ZTP connection from the Edgemarc)
  • 5671 for EMPath
    Inbound (RabbitMQ communication between EdgeMarc and EdgeView)
  • 8022, 8443 for EM GUI access
    Inbound (Communication between EdgeView and EdgeMarc)
  • 9142 for legacy support data syncing Inbound (Cassandra connection for legacy support)
  • 22 for ssh
    Inbound (Connection of EdgeMarc devices in environments that have both EdgeView14 and EdgeView15 deployed)
  • 25, 587 for SMTP
    Outbound (For EdgeView to send email notifications to users)
  • Inbound (RabbitMQ communication from EdgeView 14 to EdgeView16 for ESWAP support).


Observability Requirements

Monitor and alert on the following KPIs to ensure a successful ongoing deployment. The following should all be implemented on an automated schedule and be executed 24x7x365:

  • Synthetic Monitoring:
    • Use synthetic monitoring and a “monitoring” user to log into the EdgeView application UI, load the device collections page and produce an uptime value % report.
    • Monitor an api endpoint such as /evapi/v1/systeminfo/version.
  • Infrastructure Monitoring:
    • Utilize infrastructure monitoring to monitor the CPU, Memory and Disk % used capacity and ensure each server metric and associated disk does not exceed 75% used capacity. Additionally, set early warning thresholds at lower values (Ex: Warn: 60%, Major: 70%, Critical: 75%).
    • Utilize infrastructure monitoring to monitor number container replicas should show REPLICAS: 1/1 or 5/5 depending on the service.
  • Log monitoring:
    • The files at /var/lib/docker/containers/*/*.log should be monitored for general system events to allow for later investigation if issues occur.
    • The file at /var/log/messages (CentOS) or /var/log/syslog (Ubuntu) should be monitored for general system events to allow for later investigation if issues occur.