Page History
| Section | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
General information
This page describes the minimum hardware and software requirements necessary for deploying Axxon Datacenter operation. The full list of requirements is created final configuration (number of servers, performance, and storage capacity) is calculated individually for each customer, depending on their needs.
Server requirements
...
project based on its tasks and scale. These requirements serve as the technical basis for infrastructure planning. This page describes the baseline requirements. A complete list of checkpoints for infrastructure preparation is available in Checklist of requirements for configuring Axxon Datacenter.
Requirements for server hardware
You can use several types of servers for deployment, each performing different roles in the architecture:
...
| Server role | Minimum requirements | Function and purpose |
|---|---|---|
| Axxon One (one or three servers) |
| Peripheral servers for video processing and on-site analytics. The number is determined by the required fault tolerance |
| AxxonNet (one or three servers) |
|
|
...
| Control center. Provides a unified interface, user management, and integration |
| Service |
...
| domain (optional) |
| Hosting of supporting services (for example, portal, documentation) |
| Database servers |
| For deploying PostgreSQL, ClickHouse, and other DBMSs. Disk requirements depend on the archive size |
License Server (if hosted locally, see Private License Server) |
|
...
|
...
|
...
|
...
|
...
|
...
|
...
Requirements for host system settings
| Note | ||
|---|---|---|
| ||
When using virtualization systems, the security of the host system is the responsibility of the customer. |
...
| Alternatively, you can use AxxonSoft’s corporate cloud license server (see Public License Server) |
Requirements for video archive storage systems
| Storage type | Requirements and supported solutions |
|---|---|
Object storage (S3-compatible) | Direct integration with cloud and local S3 solutions to create a horizontally scalable archive. Public cloud services: Private/Hybrid solutions:
|
| Network-attached storage (NAS) | Usage of classic network storage devices using standard protocols.
|
Required settings of the host system and network
These settings are critical for the correct deployment and operation of the platform:
| Parameter | Requirements |
|---|---|
| Security and access | |
| Responsibility | Security of host systems (including hypervisors) is provided by the customer |
| Interserver traffic | All network connections must be allowed between all project servers (without firewall restrictions):
|
| SSH access | Required for installation and administration on Linux servers |
| Firewall | UFW is not supported and must be disabled in the OS. If necessary, you can configure the rules via iptables |
| Network configuration | |
| Open ports | The following ports are open and added to the Firewall permissions:
|
...
|
...
|
...
Permissions for access and traffic:
- All traffic between the used hosts is allowed.
- All servers are available to each other over the network.
- No port restrictions between servers.
- No network firewall between servers.
Full Internet access from the servers is provided.
- SSH access to Linux servers.
...
UFW isn't supported and must be disabled in OS. Optional port configuration must be done with Iptables.
...
| |
| Internet access | All servers must have full internet access (for installing updates, licenses, certificates, and others) |
| Time synchronization (NTP) | All servers must have an NTP server configured and functioning correctly |
| Time zone | All servers must have the required time zone set |
| Infrastructure services (delivery options) | |
| License Server |
|
| Domain name |
|
...
...
...
|
...
|
...
|
...
|
...
| SSL certificate for |
...
| a domain |
...
| name |
|
...
|
...
|
...
|
...
|
...
|
| Mail server |
...
...
|
...
|
...
|
...
|
...
|
...
|
...
| Remote | |
...
| access | |
| Procedure of remote access for support | For deployment and support work, AxxonSoft engineers require remote access to servers. The following methods are supported (in order of priority):
|
...
|
...
|
...
|
...
|
...
|
...
See also:
...