SevOne Data Insight Pre-Installation Guide

The following table lists the minimum versions required for third-party packages prior to the deployment of SevOne Data Insight 7.0.

The table below contains the default IP ranges used by SevOne Data Insight for standard deployment. If there is a conflict with the flannel CNI (Container Network Interface) IP Range, you will need to customize your deployment.

Please refer to SevOne Data Insight User Guide for information on using SevOne Data Insight and the SevOne Data Insight Administration Guide for information about administrative features.

• An NMS cluster or appliance running version 7.x.
• (Optional) A SevOne NMS User Role created for SevOne Data Insight users. You can set up a user role if you would like to specify which users have access to SevOne Data Insight. If this is not done then, all SevOne NMS users will have access to SevOne Data Insight as report consumers. For more information on creating user roles and assigning users to user roles, please refer to topic User Role Manager in SevOne NMS System Administration Guide. Role ID can be obtained from REST API's swaggerUI. For additional details, please refer to SevOne Data Insight User Guide > Administer > Tenants > User Role / Role ID in SevOne NMS > section Obtain User Role ID.

For appliance-based installation, please follow the instructions in SevOne Data Insight Appliance Insert guide to deploy each Data Insight appliance. After successful deployment, change the default password, and then proceed to section Configure Network Settings.

To deploy SevOne Data Insight .ova, deploy it on each Linux machine you plan to install Data Insight on. For details, please refer to Deploy an OVF or OVA Template (docs.vmware.com). After successful deployment of each virtual machine, please execute the following steps.

1. SSH into your SevOne Data Insight machine and log in as sevone and at the Password prompt, enter sevone.

   Log in to SevOne Data Insight machine for the 'first' time

   $ ssh sevone@<virtual machine IP address or hostname>

   
   

   Example

   $ ssh sevone@10.128.9.176

   At the password prompt, enter the default password sevone.

2. After logging in for the first time, you are required to change the password. You will get the following 3 prompts.
   1. (current) UNIX password - password when you enter SevOne Data Insight virtual machine for the first time. Password is sevone.
   2. New password - new password must be 8 characters or longer.
   3. Retype new password - retype the new password.
   
   

   Required: Change password after logging in for the 'first' time

   
   $ ssh sevone@<virtual machine IP address or hostname>
   
   sevone@<virtual machine's IP address or hostname> password: <enter 'sevone'>
   You are required to change your password immediately (root enforced)
   WARNING: Your password has expired.
   You must change your password now and login again!
   Changing password for user sevone.
   Changing password for sevone.
   (current) UNIX password: <enter 'sevone'>
   New password: <enter 'new' password>
   Retype new password: <re-enter 'new' password>
   passwd: all authentication tokens updated successfully.
   Connection to <virtual machine's IP address or hostname> closed.
   

   
   

   Example

   Enter the following values in the prompts below.

   • (current) UNIX password: sevone
   • New password: testing123
   • Retype new password: testing123

   
   $ ssh sevone@10.128.9.176
    
   sevone@10.128.9.176's password: sevone
   You are required to change your password immediately (root enforced)
   WARNING: Your password has expired.
   You must change your password now and login again!
   Changing password for user sevone.
   Changing password for sevone.
   (current) UNIX password: sevone
   New password: testing123
   Retype new password: testing123
   passwd: all authentication tokens updated successfully.
   Connection to 10.128.9.176 closed.
   

3. (optional) You may change the host name of your SevOne Data Insight virtual machine by executing the following steps.

   $ ssh sevone@<virtual machine IP address or hostname>
   
   $ sudo hostnamectl set-hostname "<enter hostname>"

   
   

   Example

   $ ssh sevone@10.128.9.176
   
   $ sudo hostnamectl set-hostname "sdi-node01"

   
   

   After resetting the hostname, log out and log back in. For the hostname to take effect, reboot.

   
   $ ssh sevone@<virtual machine IP address or hostname>
   
   $ sudo reboot

   
   

   Example

   
   $ ssh sevone@10.128.9.176
   
   $ sudo reboot
   

4. To configure the network settings, please proceed to section Configure Network Settings.

1. Change directory to /opt/SevOne/upgrade/ansible/playbooks/.

   $ cd /opt/SevOne/upgrade/ansible/playbooks/

2. Copy chrony.example.conf and snmpd.example.conf files.

   $ sudo cp /etc/chrony.example.conf /etc/chrony.conf
   
   $ sudo cp /etc/snmp/snmpd.example.conf /etc/snmp/snmpd.conf

3. Using a text editor of your choice, edit /etc/chrony.conf and/or /etc/snmp/snmpd.conf files to customize your configuration settings.
4. After all configuration changes are complete, run up.yaml for the configuration settings to take effect.

   $ sevone-cli playbook up

   
   

   Check pod status to ensure pods are completed / running

   $ kubectl get pods
   NAME                                                     READY   STATUS      RESTARTS        AGE
   di-prometheus-node-exporter-xhpqw                        1/1     Running     3 (4h19m ago)   22h
   di-prometheus-node-exporter-fnz7s                        1/1     Running     3 (4h27m ago)   22h
   di-report-tombstone-sweeper-28458480-xdppc               1/1     Running     0               4h32m
   ingress-ingress-nginx-defaultbackend-69f644c9dc-zcg8f    1/1     Running     1 (4h19m ago)   4h32m
   ingress-ingress-nginx-controller-fddc9cd4-krrzk          1/1     Running     3 (4h19m ago)   22h
   di-kube-state-metrics-6f4fbc67cb-p4tz4                   1/1     Running     0               4h32m
   di-mysql-0                                               2/2     Running     0               4h17m
   di-create-secrets-r27jf                                  0/1     Completed   0               4h1m
   di-upgrade-lp8b4                                         0/1     Completed   0               4h
   datasource-operator-controller-manager-cc766849f-qkmp7   2/2     Running     0               4h
   di-djinn-api-67b78d684f-wt8ss                            1/1     Running     0               4h
   di-assetserver-c9b5fdd5d-wkcrr                           1/1     Running     0               4h
   di-registry-85c9f98499-d4r62                             1/1     Running     0               4h
   di-scheduler-74774dbdb8-hjv5l                            1/1     Running     0               4h
   di-wdkserver-d598fc4f9-5r8qh                             1/1     Running     0               4h
   di-migrator-7d8cdddd9-5gbrs                              1/1     Running     0               4h
   di-printer-8574f88978-ps9rq                              2/2     Running     0               4h
   di-prometheus-server-6c75b49944-mmc7c                    2/2     Running     0               4h
   di-ui-56599488fc-48jdt                                   1/1     Running     0               4h
   di-redis-master-0                                        2/2     Running     0               4h
   di-graphql-6b7cf4f6b-bpcst                               1/1     Running     0               4h
   di-apikey-rotation-28459020-pnlwc                        0/1     Completed   0               38m
   di-asset-sweeper-28459045-72c4x                          0/1     Completed   0               13m
   di-user-sync-28459045-5dh8w                              0/1     Completed   0               13m
   di-asset-sweeper-28459050-sqfk6                          0/1     Completed   0               8m14s
   di-user-sync-28459050-zsstz                              0/1     Completed   0               8m14s
   di-asset-sweeper-28459055-7pm78                          0/1     Completed   0               3m14s
   di-user-sync-28459055-r8zx9                              0/1     Completed   0               3m14s
   

Now that you have deployed SevOne Data Insight, you are ready to initialize Data Insight. Please refer to SevOne Data Insight Installation Guide.