To install and configure
Download the
cd /opt/ wget ftp://$url_from_support wget ftp://$url_from_support
Enable read-write-execute permissions for the copied files using the command given below:
chmod +x install-ev.sh
Validate installation media readiness using the command given below:
pwd && ls -alh
As depicted in the example screenshot, confirm the two files exhibit approximately the same size and permissions.
Execute the following command to start installation process:
./install-ev.sh
The installation continues by installing Docker Compose, Docker and
GUI_IP - The host name or address that the users can use to access
GUI_IP must be the same as either EV_IP or EV_IP6.
EV_IP - The host name or IPv4 address for the managed devices to contact
EV_IP6 - The host name or IPv6 address for managed devices to contact
The EV_IP6 address is not set by default. If you want to access
The installation creates a log file of all actions for historical review/troubleshooting. The resultant filename is in the format of $MM-DD-YYYY-ev-install.log
You are prompted to enter information related to your networking configuration. Read this section carefully and enter the appropriate values applicable to your environment.
Once installation completes, the console screen displays the message “
To check whether the containers started successfully, use the following command:
docker ps --format "table {{.ID}}\t{{.Image}}\t{{.Status}}\t{{.Names}}"
Make sure that the STATUS is healthy. If there are unhealthy statuses, run the following command and check the Health section of the output:
docker inspect $container_name
For example:
docker inspect scc
Once the installation completes, optionally run a basic sanity check using the command given below:s
cd /opt/scc-build ; ./ev_check.sh post-install
For initial SCC configuration, register your
Refer to Manually Configure ZTP when upgrading from
If overcommit_memory is set to 0, it can cause issues with Redis container under low memory conditions.
To fix this issue:
Add vm.overcommit_memory = 1 to /etc/sysctl.conf and then reboot.
Alternatively, run the following command:
sysctl vm.overcommit_memory=1
Enter the following command as Root user:
echo never > /sys/kernel/mm/transparent_hugepage/enabled
Restart Redis once THP is disabled.
Redis container does not support overcommit_memory and Transparent Huge Pages. These entries appear in Redis log which can be checked by 'docker-compose logs redis'. The warnings in the Redis log file are as follows:
"09 Sep 2020 19:05:49.043 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
09 Sep 2020 19:05:49.043 # WARNING you have Transparent Huge Pages (THP) support enabled in your kernel. This will create latency and memory usage issues with Redis. To fix this issue run the command 'echo never > /sys/kernel/mm/transparent_hugepage/enabled' as root, and add it to your /etc/rc.local in order to retain."
Follow the instruction in the log messages to fix the WARNINGs to prevent the
Please note these changes should be on the HOST OS, not in the container.