Setting up the VM's
In this article we will show you how to deploy the OVA’s and set up the VM’s for the CryptoSpike- and Fpolicy Server.
If you haven’t already received a link to the OVA file please contact us!
Basically the CryptoSpike consists of 3 VM’s, which can easily be deployed of a OVA file.
CryptoSpike Server
CryptoSpike FPolicy Server
CryptoSpike FPolicy Server 2
So we need 3 different IP-Addresses.
The IP-Addresses should be in the same network so the latency will be kept as small as possible.
Each server runs on a Linux Debian 9.
The system requirements are:
CryptoSpike Server: 8vCPU, 16 GB RAM and 125 GB disc memory
FPolicy Server: 8vCPU, 8 GB RAM and 16 GB disc memory
To be able to load the blacklist and making updates, following URL must be reachable:
https://cryptospike.prolion.at
Following network-communication must be able:
Data LIF SVM <-> FPolicy Server (high performance, low latency)
FPolicy Server <-> CryptoSpike Server (performance ca. 40 MB/s)
CryptoSpike Server <-> ONTAP (Latency and performance are not critical)
Source: | Destination: | Port: |
---|---|---|
Hazelcast: |
|
|
FPolicy Server | CryptoSpike Server | tcp 5701 |
CryptoSpike Server | FPolicy Server | tcp 5701 |
NETTY(FPolicy Statistics): |
|
|
FPolicy Server | Cryptospike Server | tcp 18080 |
Cryptospike Server | FPolicy Server | tcp 18080 |
ONTAP: |
|
|
FPolicy Server | Data – LIF(s) | tcp 18080 |
Data – LIF(s) | FPolicy Server | tcp 18080 |
CryptoSpike Server | Cluster Mgmnt | tcp 18080 |
Cluster Mgmnt | Cryptospike Server | tcp 18080 |
Cryptospike Server | Cluster Mgmnt | tcp 80 (http) or tcp 443 (https) |
Cluster Mgmnt | Cryptospike Server | tcp 80 (http) or tcp 443 (https) |
Internal Proxy: |
|
|
FPolicy Server | CryptoSpike Server | tcp 3142 |
MySQL: |
|
|
FPolicy Server | CryptoSpike Server | tcp 3306 |
Blacklist & Updates: |
|
|
CryptoSpike Server | https://cryptospike.prolion.at |
|
Depending on setup, either: | https://cryptospike.prolion.at |
|
nor: | CryptoSpike Server | tcp 3142 |
Next step: Configuration CPanel - CryptoSpike Server
See also: Release Notes / Troubleshooting / FAQ