Ctrlk
Ops IntelligenceAsset IntelligenceObservabilityRobotic Data
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Post cfxDimensions VM Installation

Step 1: Login into Platform VM using any SSH client (ex: putty). Default username is 'macaw'

Run the following commands on the Platform VM.

sudo firewall-cmd --permanent --add-port=8080/tcp
sudo firewall-cmd reload

Step 2: Verify that NTP time is in sync on all of the cfxDimensions Platform, Service, cLambda & DB/Data nodes.

Note: On RHEL/CentOS 7.6 or above, please refer /etc/ntp.conf file. On RHEL/CentOS 8.3 or above, pleae refer /etc/chrony.conf file

To manually sync VM's time with NTP server.

RHEL / CentOS 8.3 or above: 

sudo systemctl stop chronyd
sudo chronyd -q 'server <ntp-server-ip> iburst'
sudo systemctl start chronyd

Timezone settings: Below are some of the useful commands to view / change / set Timezone on cfxDimensions VMs.

sudo tzselect
sudo timedatectl
sudo timedatectl set-timezone Europe/London

HTTP Proxy Settings:

CloudFabrix cfxDimensions platform is built on micro services architecture ontop of underlying Docker Container infrastructure. cfxDimensions platform and AIOps application service's container images are hosted on secure Docker registry running on AWS cloud.

During deployment, macaw CLI (a command line tool built by CloudFabrix to orchestrate the provisioning of cfxDimensions platform and application services) connects to CloudFabrix's Docker registry to pull the necessary container images over internet.

Note: Internet access is needed only during initial deployment and upgrades (when needed).

If there is a HTTP proxy server is deployed to control the internet access, apply the below HTTP proxy settings on all cfxDimensions Platform, Service, cLambda and DB/Data nodes.

Step 1: On cfxDimensions Platform, Service, cLambda and DB/Data nodes, edit /etc/environment file and define HTTP Proxy server settings as shown below.

Note: IP Address details are given for a reference only. They need to be replaced with appropriate HTTP Proxy server IP and port applicable to your environment.

Note: For no_proxy and NO_PROXY environment variables, please include loopback and IP addresses of all Platform, Service, cLambda and DB/Data nodes. This will ensure to avoid internal CloudFabrix AIOps application traffic going through HTTP proxy server.

Additionally, include any target applications or devices IP address or DNS names where it doesn't require to go through HTTP Proxy server.

Step 2: Configure Docker Daemon with HTTP Proxy sever settings.

Create a file called 'http-proxy.conf' under above directory and add the HTTP Proxy configuration lines as shown below.

If there is an username and password required for HTTP Proxy server authentication, and if the username has any special characters like "\" (ex: username\domain), it need to be entered in HTTP encoded format. This is applicable only for Docker daemon. Please follow the below instructions.

HTTP Encode / Decode URL: https://www.urlencoder.org

If the username is john\acme.com : The HTTP encoded value is john%5Cacme.com and the HTTP Proxy configuration looks like below.

Step 3: Restart the Platform, Service, cLambda & DB/Data node VMs to apply the HTTP Porxy server settings.

Whitelist URLs of CloudFabrix external repositories: (Internet outbound access)

Below list of URLs to be whitelisted (for outbound access only) when CloudFabrix dimentions platform is deployed in a restricted environment to access platform and application software images during the platform setup, configuration and for on going updates.

PreviouscfxDimenions on VMware vSphereNextSSL Certificates Installation

Last updated