LINMN01

Note: This are reference values to assess the system size. In reality, more parameters define real workload and affect required resources differently. Refer to Hardware Configuration Requirements to plan the actual required capacity.

Server Names	LINMN01
Description	CloudBlue Commerce management node on Linux. The server runs CloudBlue Commerce management software.
Density	Up to approx. 10,000 accounts. Refer to Hardware Configuration Requirements to plan the actual required capacity. Important: On the installations with more than 50 parallel active sessions in UX1 for Customers (in peak), the APS Booster service must be enabled. To learn more, refer to Improving System Response Speed. To evaluate current CloudBlue Commerce UI load profile, please refer to this KB article or contact CloudBlue Commerce Support team.
Quantity	1
OS	RHEL 7.4 (x64) or higher CentOS 7.4 (x64) or higher
Software	To be installed by customer: OS only Important: Do not use the Extra Packages for Enterprise Linux (EPEL) repository and do not install Redis Cache versions other than 2.4.x. Otherwise, CloudBlue Commerce will not be able to operate properly.
CPU	4 core
RAM	8 GB
Disk	500 GB, 2300 IOPS
Azure Type	F4s v2, P20
NICs	BackNet There are also additional requirements for BackNet throughput in case you are going to use APS Booster. For more details refer to Deploying UI on Web Cluster.

Important: Due to the security reasons, disable IPv6 support in the back-net network interface properties on the CloudBlue Commerce management node, UI and branding nodes.
If you use a container for deploying CloudBlue Commerce management node, UI node, open the container configuration file - /etc/sysconfig/vz-scripts/<container_id>.conf - and remove the IPv6 support for the host-only interface. If you create a new container, make sure that IPv6 support for the back-net network interface is not specified in the container creation parameters.
If CloudBlue Commerce management node, UI node is deployed on a real physical server, disable the IPv6 support in the back-net network interface using the standard functionality of the OS being installed. For instructions on how to do it, refer to the appropriate documentation of the server OS.