Vertiv TRELLIS User Manual
The TRELLIS™ Real-Time Infrastructure
Optimization Platform
Pre-Installation
Installer/User Guide
Technical Support Site
If you encounter any installation or operational issues with your product, check the pertinent section of this manual to see if
the issue can be resolved by following outlined procedures.
Visit https://www.vertiv.com/en-us/support/ for additional assistance.
TABLE OF CONTENTS
1 Preparing for the Installation 1
1.1 Minimum Deployment Requirements 1
1.1.1 Workstation 2
1.1.2 TRELLIS™ platform 2
1.1.3 Microsoft Windows OS 4
1.1.4 Red Hat Enterprise Linux OS 5
1.2 Intelligence Engines 12
1.2.1 TRELLIS™ Intelligence Engine hardware requirements and pre-requisites 12
1.3 Installation Tools 14
1.4 Environment Details 15
1.5 Network Configuration 15
1.6 Firewall Ports 17
1.7 Firewall Security 20
1.8 Provisioning Requirements 20
1.9 Partitions, Disk Space and Permissions 21
1.9.1 Windows Disk Space Usage 22
1.9.2 Red Hat Enterprise Linux Directories Partitions and Disk Space 23
1.10 Authentication 24
1.10.1 Email Notification server assignments 25
1.11 Post Installation 25
2 Network Communication 26
2.1 TRELLIS™ Intelligence Engine 26
2.2 Avocent® Universal Management Gateway Appliance 26
2.3 Ntegrity Gateway Appliance 26
2.3.1 Logical connections 26
2.3.2 Physical connections 27
2.4 Common Installation Scenarios 27
2.4.1 Installation on a separate private network for facility equipment 27
2.4.2 Best practices for Virtual Machine (VM) environments 29
Appendices 31
Appendix A: Browser Recommendations 31
Appendix B: Naming Conventions for Platform Domains 32
Appendix C: Red Hat Enterprise Linux OS Supported Time Zone List 33
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | i
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | ii
1 PREPARING FOR THE INSTALLATION
The Trellis™ Real-Time Infrastructure Optimization Platform installation process is performed by our Professional Services
team members. However, there are some activities that need to be performed by our customers before our team arrives. We
have created this guide to help you prepare for our arrival and to ensure a successful Trellis™ platform installation.
This guide includes the minimum hardware and software requirements, instructions to install the operating system, special
tools to be used during the installation and information that you need to provide to our team in advance of our arrival.
General information includes network communication, environments and installation scenarios.
NOTE: For the most current information, see the Trellis™ platform release notes.
NOTE: In this guide, the word platform refers to the Trellis™ platform.
For additional information, please see the following guides:
• The TRELLIS™ Real-Time Infrastructure Optimization Platform User Guide
• The TRELLIS™ Real-Time Infrastructure Optimization Platform Red Hat Enterprise Linux (RHEL)
Administrator's Guide
• The TRELLIS™ Real-Time Infrastructure Optimization Platform Microsoft Windows Administrator's Guide
• The TRELLIS™ Real-Time Infrastructure Optimization Platform Disaster Recovery Technical Bulletin
• Avocent® Universal Management Gateway Appliance Installer/User Guide
1.1 Minimum Deployment Requirements
The minimum requirements for the deployment of the Trellis™ platform software include a customer-supplied client
workstation and two customer-supplied, dedicated server class machines, referred to as the front and back machines. The
workstation and the front and back machines should be fully installed and equipped with the specified operating system,
tools and provisioning requirements before the Professional Services team arrives to install the Trellis™ platform software.
The workstation is used by the Professional Services team to perform the software installation and the server class machines
are used to house the Trellis™ platform. The front machine hosts the application servers and the back machine hosts the
database servers and services, such as authentication. Both the front and back machines must be accessible from the
workstation.
NOTE: The Tr ellis™ platform installers are delivered via the Content Delivery Network (CDN). Once downloaded, they
must be extracted to the front and back machines or to a network share that is accessible from both machines.
NOTE: Make sure you are using a system that has the ability to share the installation configuration. For the following
installation, an NFS/SMB system is used, which meets the sharing requirement.
NOTE: Vertiv™ supports the Trellis™ platform on physical and virtual server environments meeting the product
documentation system specifications with dedicated system resources. While best performance is generally achieved
in dedicated physical systems, virtual deployment can be effective as long as system resources are dedicated to the
Trellis™ platform Virtual Machine (VM) instance. For virtually hosted environments, Vertiv Technical Support will
make every attempt to support any issues in the same manner that they would support the software in a physical
server environment. Should an issue prove to be related exclusively to a virtually hosted environment, Vertiv
Technical Support will make all appropriate recommendations to the customer for optimal operations; assistance may
be required by the corresponding Virtual Host Solution Provider to fully resolve those environmental related issues.
The following sections provide the minimum deployment requirements for the workstation, Trellis™ platform and the
Trellis™ Intelligence Engine. For the machine and operating system requirements, see TRELLIS™ platform on page 2. For
the hardware and operating system requirements, see Intelligence Engines on page 12.
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | 1
1.1.1 Workstation
The following are the minimum hardware and software requirements for the workstation to facilitate installation of the
Trellis™ platform, version 5.0.1.1 and higher. These requirements are also applicable for the Bulk Data Processing tool. For
more about the Bulk Data Processing tool, see Data Management in The TRELLIS™ Real-Time Infrastructure Optimization
Platform User Guide.
Hardware
• Dual-core Intel Pentium 4 CPU at 2.8 GHz
• 8 GB RAM, LAN connection
Operating systems
• Microsoft Windows 10 and higher
Additional software
• Adobe Flash Player version 12 or higher
• Notepad++
• Microsoft RDP Client (if installing the Trellis™ platform on Windows)
• PuTTY (if installing the Trellis™ platform on Red Hat Enterprise Linux or configuring the Avocent® Universal
Management Gateway appliance)
• WinSCP (if installing the Trellis™ platform on Red Hat Enterprise Linux)
Browsers for the
• Google Chrome version 74.0.3729.169 or higher
• Mozilla Firefox version 63.0.3 or higher
• Microsoft Edge 42.17134.1.0 or higher
Trellis™
platform user interface
Browsers for the symbol portal
• Google Chrome version 40.0 to 63.0 and higher
Browsers for 3D features
• Google Chrome
NOTE: The recommended minimum screen resolution is 1280 x 1024.
For more information, see Browser Recommendations on page 31.
1.1.2 TRELLIS™ platform
The following are the minimum deployment requirements for the Trellis™ platform, version 4.0.3 and higher.
Front and back machines
The following are minimum requirements on both the dedicated front and back machines to facilitate installation and
operation of the Trellis™ platform.
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | 2
Table 1.1 Data Center Guidelines
COMPONENTS SMALL MEDIUM LARGE ENTERPRISE
Concurrent users 10 20 50 100
Devices 2,000 20,000 100,000 200,000
Power Connections 1,000 10,000 60,000 100,000
Data Connections 2,000 10,000 60,000 100,000
Monitored Datapoints 1,000 10,000 40,000 140,000
CPUs 2 4 4 4
CPU Cores 8 16 16 32
Table 1.2 Hardware Recommendations for the Front Machine
FRONT MACHINE HARDWARE SMALL MEDIUM LARGE ENTERPRISE
CPU manufacturer Intel® Intel® Intel® Intel®
CPU model Xeon® Xeon® Xeon® Xeon®
CPUspeed (GHz) 8 M L3 cache 2.6 2.6 2.6 2.6
CPU count 1 2 2 2
CPU cores 4 4 4 8
Memory (GB)DDR3 1333 MHz 32 32 40 44
Disk throughput > 500 MB/s (sequential) [uncached]
Storage
Ethernet > 80 MB/s
300 GB Enterprise c lass
Table 1.3 Hardware Recommendations for the Back Machine
BACK MACHINE HARDWARE SMA LL MED IUM LA RGE ENTERPRISE
CPU manufacturer Intel® Intel® Intel® Intel®
CPU model Xeon® Xeon® Xeon® Xeon®
CPUspeed (GHz) 8 M L3 cache 2.6 2.6 2.6 2.6
CPU count 1 2 2 2
CPU cores 4 4 4 8
Memory (GB)DDR3 1333 MHz 24 32 32 32
Disk throughput > 500 MB/s (sequential) [uncached]
Storage
Ethernet > 80 MB/s
*300 GB Enterprise c lass for base installation
*Hardware sizing varies depending on usage requirements and is performed by Professional Services.
Operating systems
The Trellis™ platform supports the following operating systems and software. One of the following operating systems must
be installed on both the front and back machines:
• CentOS 7.6-7.7
• Red Hat Enterprise Linux 6.10 and 7.1-7.7
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | 3
• Microsoft Windows 2012 Standard R2 and 2016 Standard
NOTE: Local administrative rights and remote desktop access are required to perform the Trellis™ platform
installation.
NOTE: The front and back machine's operating system must have regional settings set to US English and the location
set to United States.
NOTE: You must set the system locale to English US for both the front and back machines if the system locale is
different than English US. Please refer to the operating system user guide for instructions on how to change the
system locale.
1.1.3 Microsoft Windows OS
The full installation of the Windows operating system must be complete.
OS configuration
The OS configuration settings must be set up as follows for the installation directories, user configuration, security
configuration and VM requirements.
Installation directories
The Trellis™ platform is installed to the C: drive by default. If you would like the platform installed to a different location, a
symbolic link must be created to the following folders:
• c:\u01
• c:\u02
• c:\u03
• c:\u05
NOTE: Tr ellis™ platform Windows installers must be placed in c: drive folders and can no longer be run from folders
that are defined as Symbolic links.
User configuration
All Trellis™ platform startups, shutdowns, installations, patches and upgrades must be performed using a Service Account
with local Administrator privileges or by using the Administrator account.
NOTE: Always install, upgrade or patch the Trellis™ platform using the same Service Account.
Security configuration
The following are requirements for the configuration of security:
CAUTION: Disable any antivirus software prior to the installation of the Trellis™ platform. You can enable the
antivirus software after completing the installation of the Trellis™ platform.
• Disable the Windows firewall on all three profiles (domain, private and public) prior to the installation of the
Trellis™ platform.
• Disable the automatic restart after Windows updates.
• Always enable the UAC mode unless the installation is using the Administrator account.
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | 4
• From the Local Policies - Security Options - User Account Control page, change the behavior of the elevation
prompt for administrators to Elevate Without Prompting.
• Restart the operating system after applying the UAC changes.
Virtualization host requirements
The following VM platforms are supported when installing the Trellis™ platform in a virtual environment:
• Hyper-V 2012 R2 version 6.3 or higher (requires the Hyper-V Integration Services are installed on the guest
operating system of the VMs that are housing the Trellis™ platform).
• vSphere (ESXi) Hypervisor v5+ (requires all VMware tools are installed on the guest operating system of the
VMs that are housing the Trellis™ platform).
1.1.4 Red Hat Enterprise Linux OS
The Linux operating system must be installed and provisioned for both the back and front machine using the supplied
kickstart configuration file. The kickstart file ensures the operating system is ready for a successful Trellis™ platform
installation.
You will receive the kickstart installation media from the Professional Services team before the scheduled date for OS
provisioning or during the OS Requirements workshop.
NOTE: For Red Hat Enterprise Linux installations, it is important that the time zone is set to one of the supported time
zones for the Trellis™ platform. See Red Hat Enterprise Linux OS Supported Time Zone List on page 33.
Using kickstart
After obtaining the kickstart file, it must be customized to reflect the network topology of the environment. Specifically, the
IP address and identity of the front and back machines must be modified, as well as the passwords for both the root and
oracle users.
If a customer wishes to use their own kickstart configuration file, the Linux server administrator must incorporate all
supplied kickstart file configuration settings into the operating system. Failure to do so could result in issues when running
the Trellis™ platform installer.
CAUTION: Any changes to the supplied kickstart settings must be provided to the Professional Services team
prior to installing the operating system, to allow time for assessment by the Engineering team. If any
required configurations are absent, the installation may not be supported.
To locate and prepare the kickstart:
1. Copy the supplied kickstart.cfg file from the media to a location that can be reached by the front and back
machines.
2. Open the kickstart.cfg file and edit the IP addresses, netmask, gateway and host filename for the machine on
which the Red Hat Enterprise Linux operating system is to be installed. Then edit the root password and the
oracle password.
CAUTION: Underscores are not supported in host filenames. The Trellis™ platform software requires a static
IP. Changing the IP address after installation may render the software unusable.
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | 5
To boot from the kickstart scripts to install the Red Hat Enterprise Linux libraries:
1. While booting at the virtual console of the back machine, press F1.
2. To make sure that distribution is supported, at the boot prompt enter linux rescue_ to boot off a USB and load
the available drivers. Using this technique, you can confirm the names of the hard drives (usually /dev/sda) and
the name of the network device. If the devices are not supported, you may need to follow the instructions
provided by Red Hat Enterprise Linux to get the latest drivers for your hardware and make sure the
distribution supports the hardware. See the documentation for RHEL7 at Red Hat Linux for more information.
3. To verify the devices are readable, enter the IP address, netmask and so on, for the back machine.
Example: Back Machine Information
linux ip=192.168.0.50 netmask=255.255.255.0 gateway=192.168.0.1 ksdevice=eth0
ks=nfs:192.168.0.1:/mnt/exports/front.cfg
4. While running the Anaconda installer, execute the kickstart scripts, then verify Red Hat Enterprise Linux
indicates up and booting is displayed.
5. Repeat this procedure to install Red Hat Enterprise Linux on the front machine using another modified version
of the kickstart scripts. Remember to enter the IP address for the front machine.
OS configuration
If not using the supplied kickstart file, the configuration settings must be set up as follows for the installation directories,
users, groups, environment variables, additional files and services, sudoers content, system, required services and security.
Installation directories
The Trellis™ platform is installed to the root by default. If you would like the platform installed to a different location, a
symbolic link must be created (as root) to the following folders:
• /u01
• /u02
• /u03
• /u05
NOTE: Tr ellis™ platform Windows installers must be placed in c: drive folders and can no longer be run from folders
that are defined as Symbolic links.
User configuration
All Trellis™ platform startups, shutdowns, installations, patches and upgrades must be performed using the “oracle” user.
The /etc/passwd file should have the oracle user and the SLI user set up and the home directory should be set to
“/home/oracle:/bin/bash.”
The "runuser -l oracle -c 'umask'" command returns either 0000 or 0002.
Group configuration
Make sure the oinstall and dba groups in the /etc/group file are set up correctly. For the oracle/oinstall, make sure the
users/user groups are configured as follows:
NOTE: The oracle user must be part of the oinstall and dba group.
• #create user and group
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | 6
• /usr/sbin/groupadd oinstall
• /usr/sbin/groupadd dba
• /usr/sbin/useradd -g oinstall -G dba oracle
• /usr/sbin/usermod -g oinstall -G dba oracle
• id oracle
Environmental variables configuration
The following environmental variables should be set for the oracle user:
• PATH should contain /sbin/
• MW_HOME=/u01/fm/11.1.1.7/
• ORACLE_HOME=/u01/app/oracle/product/12.1.0.2
• ORACLE_SID=orcl
Additional required files
The following file exists with the following permissions set:
• /etc/oraInst.loc = -rw-r--r-- (root)
The /etc/oraInst.loc file contains the following lines:
• inventory_loc=/u01/app/oraInventory
• inst_group=oinstall
The following file exists with the following permissions set:
• /etc/oratab = -rw-rw-r-- (oracle:oinstall)
For Linux® 6.x ONLY, the following symlinks should be created and the files exist:
• libcrypto.so.1.0.0 -> /usr/lib/libcrypto.so.10
• libssl.so.1.0.0 -> /usr/lib/libssl.so.10
Additional services required
The /etc/xinetd.d/nodemanager file exists and content is identical to the following:
service nodemgrsvc
{
type = UNLISTED
disable = yes
socket_type = stream
protocol = tcp
wait = yes
user = root
port = 5556
flags = NOLIBWRAP
log_on_success += DURATION HOST USERID
server = /bin/su
server_args = - oracle -c /u01/trellis/startNodeManager.sh
}
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | 7
Sudoers content
The "runuser -l oracle -c 'sudo -l' | grep "(root)" command lists out "(root) NOPASSWD:" for the following entries:
• /etc/init.d/trellis
• /u03/root/disable_escalation.sh
• /u03/root/enable_nodemanager.sh
• /u03/root/ohs_enable_chroot.sh
• /u03/root/postinstall_env_setup.sh
• /u03/root/preinstall_env_setup.sh
• /u03/root/sli_install.bin
NOTE: If this cannot be determined, the Sudoers file MUST match engineering specifications, as per the kickstart file.
System settings
The "/etc/sysctl.conf" file MUST contain the required parameters for the Trellis™ platform and should meet the following
requirements:
• kernel.sem = "250 32000 100 128"
• net.ipv4.ip_local_port_range = "9000 65535"
• fs.aio-max-nr >= 1048576
• fs.file-max >= 6815744
• kernel.shmall >= 4194304
• kernel.shmmax >= 536870912
• kernel.shmmni >= 4096
• net.core.rmem_default >= 262144
• net.core.rmem_max >= 4194304
• net.core.wmem_default >= 262144
• net.core.wmem_max >= 1048586
• kernel.random.write_wakeup_threshold = 1024
The /etc/security/limits.conf file exists and content contains the following:
• oracle soft nproc 2047
• oracle hard nproc 16384
• oracle soft nofile 1024
• oracle hard nofile 65536
• oracle soft stack 10240
The /etc/pam.d/login file exists and content contains the following:
• session required /lib64/security/pam_limits.so
Required packages for Red Hat Enterprise Linux version 6.x and 7.x
The following are the required packages for Linux version 6.x:
• mtools
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | 8
• pax
• python-dmidecode
• kexec-tools
• fipscheck
• device-mapper-multipath
• sgpio
• emacs
• libsane-hpaio
• xorg-x11-utils
• xorg-x11-server-utils
• binutils
• compat-db
• compat-libcap1
• compat-libstdc++-33
• compat-libstdc++-33.i686
• device-mapper-multipath
• dos2unix
• elfutils-libelf
• elfutils-libelf-devel
• gcc
• gcc-c++
• glibc
• glibc.i686
• glibc-common
• glibc-devel
• glibc-devel.i686
• kexec-tools
• ksh
• libaio
• libaio.i686
• libaio-devel
• libaio-devel.i686
• libgcc
• libgcc.i686
• libsane-hpaio
• libstdc++
• libstdc++.i686
• libstdc++-devel
• libstdc++-devel.i686
• libXext
• libXi
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | 9
• libXtst
• make
• openmotif
• openssl.i686
• redhat-lsb
• redhat-lsb-core.i686
• sgpio
• sysstat
• unixODBC
• unixODBC-devel
• xinetd.x86_64
• iptraf
• nmap
• screen
• strace
The following are the required packages for Red Hat Enterprise Linux version 7.x:
• mtools
• pax
• python-dmidecode
• kexec-tools
• fipscheck
• device-mapper-multipath
• sgpio
• emacs
• libsane-hpaio
• xorg-x11-utils
• xorg-x11-server-utils
• binutils
• compat-db
• compat-libcap1
• compat-libstdc++-33
• compat-libstdc++-33.i686
• device-mapper-multipath
• dos2unix
• elfutils-libelf
• elfutils-libelf-devel
• gcc
• gcc-c++
• glibc
• glibc.i686
Vertiv | The TRELLIS™ Real-Time Infrastructure Optimization Platform | 10
Loading...