You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

In this section:


This section provides a detailed description about the requirements to install 

Unable to show "metadata-from": No such page "_space_variables"
.

Unable to show "metadata-from": No such page "_space_variables"
 Installation Files

The installation files can be downloaded from a remote web server to the / opt directory of your Linux server.

To install 

Unable to show "metadata-from": No such page "_space_variables"
, the installation file needs to be deployed using our installation script as described in this document.  

Requirements

Minimum Requirements:

  • CentOS 7 or Ubuntu 18 Virtual Machine. 
    • This should be a dedicated virtual machine with no other production applications running. Base OS packages should be installed and updated to the latest versions.
    • Internet connectivity. This is used to automatically install and configure software dependencies.
  • vCPU/Core: 4
    • Example: Intel(R) Xeon(R) Platinum 8175M CPU @ 2.50GHz
  • RAM: 16 GB
  • NIC interface: 1
  • Disks mounted to the Virtual Machine: 2*
    • Host OS: 100 GB minimum
    • Unable to show "metadata-from": No such page "_space_variables"
      /Docker storage: 
      • Recommended 1 TB. Minimum 500 GB.
      • Disk space monitoring and alerting configured at safe threshold (for example, 80% used capacity)
      • Ability to expand disk space when it reaches threshold.
  • Docker version 18.09.6
  • Docker Compose version 1.24.0

*An additional disk/file system should be configured and mounted at /var/lib/docker/ prior to any installation activities. This provides greater flexibility and reliability on production systems. A sample configuration guide is provided under Configuring Storage for EdgeView and Docker section.

Note

It is possible to install

Unable to show "metadata-from": No such page "_space_variables"
on a bare metal server. In this case, it is recommended to manage the storage provided to the OS through a logical volume manager to enable redundancy and to enable the ability to expand storage capacity over time. Due to the operation complexity of such an installation it is not recommended for most environments and the configuration of such an environment is considered outside the scope of this document.

Network Port Requirements:

The following ports should be open for successful 

Unable to show "metadata-from": No such page "_space_variables"
installation:

  • 80, 443 for HTTP/HTTPS
    Inbound (
    Unable to show "metadata-from": No such page "_space_variables"
    GUI access and initial ZTP connection from
    Unable to show "metadata-from": No such page "_space_variables"
    )
  • 5671 for EMPath
    Inbound (RabbitMQ communication between 
    Unable to show "metadata-from": No such page "_space_variables"
    and
    Unable to show "metadata-from": No such page "_space_variables"
    )
  • 8022, 8443 for EM GUI access
    Inbound (Communication between 
    Unable to show "metadata-from": No such page "_space_variables"
    and
    Unable to show "metadata-from": No such page "_space_variables"
    )
  • 9042 for legacy support data syncing
    Inbound (Cassandra connection for legacy support)
  • 22 for ssh
    Inbound (Connection of 
    Unable to show "metadata-from": No such page "_space_variables"
    devices in environments that have both
    Unable to show "metadata-from": No such page "_space_variables"
    14 and
    Unable to show "metadata-from": No such page "_space_variables"
    15 deployed)

VM sizing chart:

Unable to show "metadata-from": No such page "_space_variables"
Configuration
4CPU/16GBRAM8CPU/32GBRAM
EdgeMarcs/Calls per second/Active users1000/30/303000/60/60

Testing Environment:

  • CentOS 7.6.1810
  • Docker 18.09.6
  • Docker Compose 1.24.0
  • Unable to show "metadata-from": No such page "_space_variables"
     15.4.0
  • Infrastructure/Hardware: AWS m5 instances
Note

Capacity numbers will vary based on a variety of factors. Please use the above information as a reference point to inform your own deployment based on your specific hardware and associated environment. 

 



 


  • No labels