SevOne Data Platform Deployment on Amazon Web Services

Amazon Web Services (AWS) is a collection of several popular cloud-based services hosted by Amazon. Introducing AWS to SevOne Data Platform has its benefits:

• Ability to deploy in AWS
• Similar to how SevOne monitors Customer Premises Equipment (CPE), routers, switches, servers, and firewalls today, it will continue to provide the same capability with AWS
• Monitoring data sources with AWS may eliminate data transport costs

In order to properly deploy SevOne NMS / SevOne Data Insight / SD-WAN (Versa / Viptela solution) on AWS, it is important to understand the following concepts.

• Key Pair - A key pair is required for initial connection to the AWS EC2 instance after deployment from AMI. For additional details, please refer to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html
• VPN Configuration - Recommended to access the system via the VPN. For additional details, please refer to https://aws.amazon.com/premiumsupport/knowledge-center/create-connection-vpc/
• Creating Security Groups - Recommended to disallow access outside of the VPN. For additional details, please refer to https://docs.aws.amazon.com/efs/latest/ug/accessing-fs-create-security-groups.html

Execute the steps below.

1. Please download the OVA images from IBM Passport Advantage (https://www.ibm.com/software/passportadvantage/pao_download_software.html) via Passport Advantage Online. However, if you are on a legacy / flexible SevOne contract and do not have access to IBM Passport Advantage but have an active Support contract, please contact IBM SevOne Support.
2. Click on the Image Id link to login to your AWS account to select an Amazon Machine Image instance type for the SevOne Appliances.
   Important: Please make sure you have the login/password for your AWS account prior to proceeding further.
3. To deploy, please refer to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/LaunchingAndUsingInstances.html for instructions. For example,
   • Choose the desired r6i instance type to configure the instance details.
     
     Note: Configuring instance details vary depending on your needs. It is important to select any Placement Group options now as this may not be changed later. It is important to select the Network options so that your instance can poll or receive streaming data from the sources that it needs.
   • Add storage. Please refer to section AWS Instance Types for SevOne Appliances above to select your desired storage.
     
     Important:
     The root disk should be 600 GiB for SevOne NMS Appliances and 250 GiB for SevOne Data Insight and SD-WAN (Versa / Viptela solution).
     
     Additional storage is required for:

     • SevOne NMS appliances PAS60K or above
     • DNC models DNC300 or above
   • Add the tags. Tags are useful to identify machine instances so they can be easily found.
   • Configure the security group. This is customer-specific. It is best to pre-configure the security group.
   • Review your configuration and launch AWS.
   • Select an existing key pair or create a new one.
     Note: You will not be able to access the new instance via SSH without the private key.

1. SSH to the Virtual Machine as root without a password and using the Key Pair selected during the Virtual Machine creation. To convert key pairs to popular SSH clients, please refer to https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-%20key-pairs.html
2. Set a root password.

   passwd root

3. Using a text editor of your choice, create /opt/aws_setup.sh file. This file is not available automatically and you must create it.

   
   touch /opt/aws_setup.sh
   

4. Edit /opt/aws_setup.sh file.

   
   vi /opt/aws_setup.sh
   

5. Add the following script to configure the data disk and run the script manually with bash.
   
   Important: If an empty data disk is attached to a virtual machine on first boot, it will be automatically formatted, mounted, and configured. However, if the user has already booted and now wants to attach a /data disk, run the script below.
   
   Example: aws_setup.sh

   
   # This script is only valid during initial deployment, and should not be used 
   # to migrate data on an existing environment with a significant amount of 
   # collected historical data
   set -e
   
   MIN_SIZE=$((150 * 1024 * 1024 * 1024))
   DATA_SIZE=$(df -B1 /data 2>/dev/null | awk 'NR==2 {print $3}')
   if [[ "$DATA_SIZE" =~ ^[0-9]+$ ]] && (( DATA_SIZE > MIN_SIZE )); then
   	MIN_SIZE=$DATA_SIZE
   fi
   DISK_NAME=$(lsblk -o NAME,FSTYPE,SIZE -Jb | jq -r --argjson minSize "$MIN_SIZE" '[.blockdevices[] | select((.children|length==0) and (.size|tonumber >= $minSize) and (.fstype|not))] | max_by(.size|tonumber) | select(.) | .name')
   
   if [ -z "$DISK_NAME" ]; then
   	echo "No appropriate blank disks found" >&2
   	exit 1
   fi
   
   systemctl stop nms
   mkdir -p /data_temp /data
   mv /data/* /data_temp
   
   mkfs.xfs /dev/$DISK_NAME
   cat > /etc/systemd/system/data.mount <<__DATA_MOUNT__
   [Unit]
   Description=Mount unit for /data
   Before=nms_deployment.service prometheus_deployment.service collectors_deployment.service
   
   [Mount]
   What=/dev/$DISK_NAME
   Where=/data
   Type=xfs
   DirectoryMode=0755
   
   [Install]
   WantedBy=multi-user.target
   __DATA_MOUNT__
   
   systemctl daemon-reload
   systemctl enable data.mount
   systemctl restart data.mount
   mv /data_temp/* /data
   systemctl start nms
   rmdir /data_temp
   

Please refer to SevOne Data Insight Pre-Installation Guide for additional details.

Please refer to SevOne Data Insight Pre-Installation Guide for additional details.

Please refer to SevOne NMS Appliance Configuration Guide for details on how to set the correct application configuration for the customer's license type and count.

Please refer to SevOne NMS documentation for details as they apply to the Virtual Appliance running on the cloud as well.

Please refer to SevOne NMS documentation for details as they apply to the Virtual Appliance running on the cloud as well.

Logon to the SevOne NMS via SSH and execute the following command.

podman exec -it nms-nms-nms /bin/bash

SevOne-act check checkout

Currently, the command returns several errors as shown in the example below. Please disregard these errors until after SevOne NMS is updated to include checks for Amazon's AWS AMI deployed instances.

Example

podman exec -it nms-nms-nms /bin/bash

SevOne-act check checkout

[ FAIL ] Rpm summary - 16 errors found, Run 'SevOne-act check rpm' for more information
[ FAIL ] Lsof summary - 2 errors found, Run 'SevOne-act check lsof' for more information
[ FAIL ] UuidsCheck summary - 1 error found, Run 'SevOne-act check uuids-check' for more information

At the time of writing, SevOne-change-ip commands are unable to respect the AWS network configuration and should not be used to change IP addresses.