SevOne Documentation
All documentation is available from the IBM SevOne Support customer portal.
© Copyright International Business Machines Corporation 2024.
All right, title, and interest in and to the software and documentation are and shall remain the exclusive property of IBM and its respective licensors. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of IBM.
IN NO EVENT SHALL IBM, ITS SUPPLIERS, NOR ITS LICENSORS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF IBM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND IBM DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT.
IBM, the IBM logo, and SevOne are trademarks or registered trademarks of International Business Machines Corporation, in the United States and/or other countries. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on ibm.com/trademark.
Microsoft Azure is a cloud computing service created by Microsoft for building, testing, deploying, and managing applications and services through Microsoft-managed data centers. Introducing Microsoft Azure to SevOne Platform has its benefits such as,
Ability to deploy in Microsoft Azure.
Similar to how SevOne monitors Customer Premises Equipment (CPE), routers, switches, servers, and firewalls today, it will continue to provide the same capability with Microsoft Azure.
Monitoring data sources with Microsoft Azure may eliminate data transport costs.
In order to properly deploy SevOne NMS / SevOne Data Insight on Microsoft Azure, it is important to understand the following concepts.
SevOne Concepts |
|
CentOS |
The OS driving the SevOne appliance. |
SevOne NMS |
The SevOne NMS appliance. |
SevOne Data Insight |
The SevOne Data Insight appliance. |
Azure Concepts related to SevOne |
|
APM Portal |
Azure Platform Management - the Graphical User Interface for Azure. |
AZ CLI |
The command line interface for Azure. |
Region |
The Azure region for deployment. This is analogous to multiple data centers in a large geographic area. |
VHD |
Virtual Hard Disk - the raw image from which an instance is created. VHDs are generated by SevOne and are made available to customers. |
SevOne Instance |
License Count |
Azure Instance Type |
Root Disk (GiB) |
Data Disk (GiB) |
vPAS5k |
Up to 5k objects |
Standard_D2s_v3 |
600 |
n/a |
vPAS10k |
Up to 10k objects |
Standard_D4s_v3 |
600 |
n/a |
vPAS20k |
Up to 20k objects |
Standard_D4s_v3 |
600 |
n/a |
vPAS60k |
Up to 60k objects |
Standard_D8s_v3 |
600 |
1,250 |
vPAS100k |
Up to 100k objects |
Standard_D8s_v3 |
600 |
2,000 |
vPAS200k |
Up to 200k objects |
Standard_D32s_v3 |
600 |
4,000 |
vDNC100 |
Up to 100 interfaces |
Standard_D8s_v3 |
600 |
400 |
vDNC300 |
Up to 300 interfaces |
Standard_D16s_v3 |
600 |
800 |
vDNC1000 |
Up to 1000 interfaces |
Standard_D32s_v3 |
600 |
1,500 |
vDNC1500 |
Up to 1500 interfaces |
rStandard_D32s_v3 |
600 |
3,000 |
The average Input / Output Operations Per Second (IOPS) is 19,000KBs.
It is very important that you follow the information in the table above. Any deviation will cause undesired results and lack of support.
Download the VHD image(s) 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 SevOne Support .
Azure customers will create an Azure page blob from a VHD in the SevOne Microsoft Azure storage account. This blob will be used to create the Azure image.
For details, please refer to https://docs.microsoft.com/en-us/azure/storage/blobs/storage-quickstart-blobs-portal
Azure Virtual networks must have VPN connectivity.
SevOne NMS image must be uploaded to your Azure storage account.
Upload the version of SevOne NMS VHD image you received to a container in your Azure storage account, saving the URL to the uploaded VHD for a later step. Each SevOne NMS version only needs to be uploaded once.
Login to the Azure portal.
Navigate to Storage Accounts.
Click the + Create button.
Click the link under Instance Details for If you need to create a legacy storage account type, please click here.
Complete the following fields.
Subscription - select your subscription.
Resource Group - select an existing or create a new resource group.
Storage account name - for example, sevoneimages. (you must specify a name that is unique across all of Microsoft Azure)
Location - specify your region.
Performance - Standard
Account kind - Storage (general purpose v1).
Replication - Locally-redundant storage (LRS).
Click Review + create.
Click Create.
Click Go to resource after the deployment has completed.
Click + Container and complete the following fields.
Name - sevone
Public access level - Blob (anonymous read-access for blobs only).
Upload SevOne image to the sevone container in your storage account via Microsoft Azure Storage Explorer (fastest / recommended) or Azure Portal Graphical User Interface.
Create SevOne NMS OS Disk for the Virtual Machine (VM) and create the instance from the OS disk.
Login to the Azure portal.
Click the + Create button and complete the following fields.
Subscription - select your subscription.
Resource Group - select an existing or create a new resource group.
Disk Name - VM1 (Replace VM1 with your intended VM hostname).
Region - specify your region.
Source type - storage Blob.
Source blob - specify the HTTP URL to the uploaded SevOne image or click browse to select it via Graphical User Interface.
OS type - Linux
VM generation - Gen 1
Size - click the link for Change size at the bottom.
Disk SKU - premium SSD (locally-redundant storage).
Custom disk size (GiB) - 600
Click OK.
Click Review + create.
Click Create.
Click Go to resource.
Click + Create VM button.
Subscription - select your subscription.
Resource Group - select an existing or create a new resource group.
VM Name - VM1 (Replace VM1 with your intended VM hostname).
Region - specify your region.
Size - select the correct Azure Instance Type from the table Azure Instance Types for SevOne Appliances.
Public Inbound Ports - allow selected ports.
Select inbound ports - check the boxes for HTTP, HTTPS, SSH.
Licensing type - Other
Click the Next : Disks > button.
Click Create and attach a new disk.
Skip this step if the data disk size for your SevOne NMS model is specified as n/a in table Azure Instance Types for SevOne Appliances.
Size - click the link for Change size at the bottom
Custom disk size (GiB) - specify the Data Disk (GiB) size for your SevOne NMS model in table Azure Instance Types for SevOne Appliances.
Click OK.
Click OK again.
Click Next : Networking > button.
Virtual Network - specify the appropriate virtual network.
Subnet - specify the appropriate subnet.
Public IP - None
Click the Review + create button and click Create.
It will take approximately 5 or more minutes to create a Virtual Machine.
During key generation, SSH will be unavailable. Please wait for SSH to become available after all SevOne processes have started.
The following steps apply to SevOne NMS only.
Using ssh, log in to SevOne NMS.
Set the SevOne root password.
Run /opt/azure_setup.sh script to complete the setup.
$
bash
/opt/azure_setup
.sh
You are now ready to login to your SevOne Virtual Machine in Azure via the Graphical User Interface, upload a license file, configure appliance model and size, and start monitoring your network.
If this is being used as a DNC, please refer to SevOne NMS Appliance Configuration Guide for details.
Please refer to SevOne NMS Appliance Configuration Guide for details on how to s et the correct application configuration for the customer's license type and count.