SevOne NMS Installation Guide

Edit online

About

Edit online

The SevOne NMS software is loaded on your appliance. If you provide the IP address of the appliance to your SevOne Sales Engineer this has been entered for you.

This document describes what you must do to get the appliance up and running from the moment you open the box until you are ready to log on to the application. Please refer to SevOne NMS Implementation Guide for how to log on, how to build a SevOne cluster, and how to begin your SevOne implementation.

Note: Terminology usage...

In this guide if there is,

  • [any reference to master] OR
  • [[if a CLI command contains master] AND/OR
  • [its output contains master]],

    it means leader.

And, if there is any reference to slave, it means follower.

Create Support Account

Edit online

To create a user account to enable SevOne Support engineers to provide support services, go to https://www.ibm.com/mysupport/. Or, contact SevOne Support via phone.

  1. In the address field on your web browser enter https://www.ibm.com/mysupport/ and press Enter.
  2. In the Create New Account section enter the following information.
    • Your Full Name
    • Email Address
    • Phone Number
    • Company
  3. Click Create Account.
  4. Your account is created instantly. SevOne Support reviews the account validity within the next business day for account activation.

Multi-Peer and Hot Standby Appliance Implementations

Edit online

The Cluster Manager provides an Integration tab to enable you to build your cluster and to add new appliances as peers into an existing cluster. Please refer to SevOne NMS Implementation Guide for details.

When your new appliance is a Hot Standby Appliance, perform the steps in chapter 2 to rack up and define the Configuration Menu settings then contact SevOne Support to ensure that the Hot Standby Appliance is appropriately implemented.

Hardware Requirements

Edit online
Important: In a cluster that contains mixed sized appliances, the largest hardware capacity appliance should be the Cluster Leader. There is RAM overhead exerted on the Cluster Leader based on its additional responsibilities. Due to this, SevOne strongly advises you to implement this recommendation.
Note: The average disk Input / Output Operations Per Second (IOPS) requirement for all appliance types is 19,000KBs.
The minimum NIC speed is 1Gbps or higher.
RAID controller requires legacy boot (non-UEFI) with 512 byte block size in RAID6 (recommended).
Important: SevOne Network Management System (NMS) version 6.8.0 and onwards offers users the flexibility to utilize their own hardware for physical installations. It is crucial to ensure that the hardware specifications align with the minimum requirements outlined in the table below, corresponding to the specific appliance model being deployed. Please note, it is perfectly acceptable for your hardware to surpass these specified requirements. However, it is essential that the hardware is fully compatible with Red Hat Enterprise Linux (RHEL) 8 for optimal performance and functionality. This approach not only allows for customization based on individual needs but also ensures a seamless integration with the SevOne NMS.
Name/Spec CPUType CPUCount TotalCores RAM (GB) DiskType FlowLimit (FPS)
PAS5K 8 Core @ 2.10Ghz 2 16 32 5x 480GB SSD 2.5" 4,500
PAS10k 8 Core @ 2.10Ghz 2 16 32 5x 480GB SSD 2.5" 10,000
PAS20k 8 Core @ 2.10Ghz 2 16 32 5x 480GB SSD 2.5" 20,000
PAS40K 10 Core @2.20Ghz 2 20 96 5x 960GB SSD 2.5" 40,000
PAS60K 10 Core @2.20Ghz 2 20 96 5x 960GB SSD 2.5" 60,000
PAS300K 12 Core @2.6Ghz 2 24 288 8x 1.92TB SSD 2.5" 80,000
DNC400 10 Core @2.20Ghz 2 20 96 5x 960GB SSD 2.5" 80,000
DNC1000 12 Core @ 2.30Ghz 2 24 96 8x 480GB SSD 2.5" 80,000
DNC1500HF 12 Core @ 2.30Ghz 2 24 128 6x 1.92TB SSD 2.5" 160,000

Appliance Network Configuration

Edit online

For advanced network configuration, use nmtui. Please refer to https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/networking_guide/sec-configuring_ip_networking_with_nmtui for details.
Time and Date can be configured using timedatectl command. For details, please refer to https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/chap-configuring_the_date_and_time.
To configure NTP/Chrony, please refer to https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/system_administrators_guide/ch-configuring_ntp_using_the_chrony_suite/ for NTP/Chrony details.
SNMP Settings can be performed manually but updating /config/snmp/snmpd.d/90-custom.conf file.

Note: Once you have gained access to the appliance and the appliance is part of the cluster, use SevOne-change-ip scripts to change the configuration of the appliance.
Note: For details on advanced Network Configurations such as configuring peer communication over NAT, please refer to SevOne NMS Advanced Network Configuration Guide for details.

OS-level User Names and Passwords

Edit online

You will need to change the default password for the support user account. This is important for security reasons.

Failure to change the default password presents a significant security risk. This publication includes the default password and is available to the public.

Change Support Password

Edit online

The support password should be changed on all peers. Perform the following steps to change the password for support.

  1. SSH into your SevOne NMS appliance and log in as support.
  2. At the Password prompt, enter supportuser.
    commandLine_supportAcct

  3. You will be prompted and required to change the support user password. Enter a new password when prompted.
  4. Exit the session when you are done.
Important: Change IP Address, Configure Network Bonding

For details on how to change the IP address on a SevOne appliance or how to configure networking bonding, please refer to the respective sections in SevOne NMS Advanced Network Configuration Guide.

Shut Down and Reboot SevOne NMS

Edit online

SevOne NMS can run for extended periods of time. Occasionally it is necessary to shut down or reboot an appliance. SevOne NMS stores data in cache and writes to the disk on a regular basis.

The following shell commands back up the memory ring tables to the database on the disk to ensure that you do not lose data.

Shutdown SevOne NMS
To shutdown SevOne NMS, you must run the command from the NMS container and not the host. 


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

$ SevOne-shutdown shutdown

Reboot SevOne NMS
To reboot SevOne NMS, you must run the command from the NMS container and not the host.


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

$ SevOne-shutdown reboot