FAQs

The default port is 9443. You may change the port from SevOne NMS > Administration > Cluster Manager > Cluster Settings tab > Ports subtab > field SevOne-gui-installer Port. After changing the port, you must regenerate the installer URL from Administration > Cluster Manager > Cluster Upgrades tab > click Run Installer.

SevOne recommends you to use any free port (i.e., port that is not used by any other service) in the range 1024 - 65535.

Execute the following command to check port availability.

$netstat -anp |grep tcp |grep LISTEN |grep <port_number_desired>

1. ssh support@<NMS appliance>
2. You need to run as root. Enter the following command to run/switch to root.

   
   sudo su

3. Start the GUI installer from the host.

   
   systemctl start sevone-gui-installer

Self-Service Upgrade running on gunicorn server uses the self-signed certificates of the nginx server by default.

"SSL_CERT_PATH": "/secrets/nginx/nginx.crt",
"SSL_KEY_PATH": "/secrets/nginx/nginx.key"

Execute the following command to restart gunicorn.

systemctl restart sevone-installer-gunicorn

If the custom certificate is based on hostname, execute the following steps.

1. Using a text editor of your choice, edit /opt/sevone_installer/SevOne-django-settings.sh file.

   vi /opt/sevone_installer/SevOne-django-settings.sh

2. Update the variables.

   # Change IP, HOSTNAME (variables value to hostname or ip address
   # whichever set in valid SSL cert), SSL_CERT_PATH & SSL_KEY_PATH
   IP='<hostname_of server>'
   HOSTNAME='<hostname_of_server>'

   Note: /opt/sevone_install/SevOne-django-settings.sh file contains the following by default.

   # Use nginx cert and key, generate open-ssl if (nginx cert/key) doesn't exist.
   NGINX_CERT='/secrets/nginx/nginx.crt'
   NGINX_KEY='/secrets/nginx/nginx.key'
   
   if [[ -f "$NGINX_CERT" && -f "$NGINX_KEY" ]];
   then
   SSL_CERT_PATH="$NGINX_CERT";
   SSL_KEY_PATH="$NGINX_KEY";

3. Run SevOne-django-settings.sh script.

   ./opt/sevone_installer/SevOne-django-settings.sh

4. Restart gunicorn.

   systemctl restart sevone-installer-gunicorn

The upgrade script, SevOne-validate-image, creates the following files.

• /opt/sevone_installer/config.json
• /opt/sevone_installer/build/static/env.json

Variable SEVONE_INSTALLER_BIND_IP in config.json file contains the IPv6 address or the IP address / FQDN of the Cluster Leader stored in the peers table.

In case where proxy is set, the config.json and env.json files must be updated manually and the installer service must be restarted. Execute the following steps.

• Using a text editor of your choice, edit /opt/sevone_installer/config.json to change the IP address to the proxy IP address / FQDN of the Cluster Leader in variable SEVONE_INSTALLER_BIND_IP. If you are using certificates, then FQDN of the Cluster Leader must be assigned to variable SEVONE_INSTALLER_BIND_IP.
• Using a text editor of your choice, edit /opt/sevone_installer/build/static/env.json to change the IP address to the proxy IP address / FQDN of the Cluster Leader in variable url. If you are using certificates, then FQDN of the Cluster Leader must be assigned to variable url.
• Change directory to /opt/sevone_installer.

cd /opt/sevone_installer

python3 manage.py collectstatic

Restart the installer service

systemctl restart sevone-installer-gunicorn.service

The upgrade artifact must be placed in /data/upgrade directory of the active Cluster Leader for the installer to detect an upgrade. If the SevOne NMS cluster is already on the target version, the installer will not detect an available upgrade path and return a message that no update is available.

If pre-checks fail, you will not be allowed to continue with the upgrade. This is intentional. SevOne does not support forcing an upgrade on corrupted environments. However, you can force an upgrade from the CLI, just like before, and then monitor the progress from the User Interface.

If upgrade fails, you may download the cluster and/or individual peer logs and contact SevOne Support from the link in error message. For debugging, old steps of checking the upgrade in screen and logs/retry attempts all remain the same.

No. Two upgrades cannot be run at the same time. If an upgrade is running and a new installer instance is launched, it will show the status of the ongoing upgrade only.

No. All peers must be reachable from the Cluster Leader to run an upgrade. The requirements are the same as before. However, if after starting an upgrade, a peer becomes unreachable, you can see its status on the installer's User Interface and the upgrade will stop, like before.

Nothing has changed here. Like before, the installer does not handle HSA failover. If there is a failover after setting up the installer, the setup will have to be done separately on the now active Cluster Leader.

• Make sure you are accessing the URL with https and, accept the certificate warning.
• Check the status of the installer service systemctl status sevone-installer-gunicorn.service.
• If systemctl status sevone-installer-gunicorn.service is running and you are still unable to access the URL then, check the gunicorn log file for more details.
  • /var/log/SevOne-gui-installer/gunicorn.log OR
  • /var/log/SevOne-gui-installer/access.log
• Check request status codes 500 or 404 in /var/log/SevOne-gui-installer/access.log.

No. The installer has to be run from the active Cluster Leader only.

• Check log files in /var/log/SevOne-gui-installer/.
• Stop installer service systemctl stop sevone-installer-gunicorn.service if it is running.
• Using the text editor of your choice, edit /opt/sevone_installer/sevone_installer/settings.py file. Change variable DEBUG to TRUE.
• Run development web server like python3 manage.py runserver 0.0.0.0:1234.

Please refer to section expand logical volume.

Please refer to AWS Quick Start Guide for details.

Latest versions of Chrome, Firefox, and Safari are supported. Internet Explorer (IE) is not supported.

Upgrade
Please refer to Upgrade Timings for Small & Large Clusters for an approximate time it will take for an upgrade.

Downgrade
Please refer to Downgrade Timings for Small & Large Clusters for an approximate time it will take for a downgrade.