QuadStor VTL Setup Notes

https://www.quadstor.com/vtl-extended-edition-downloads.html
https://www.quadstor.com/virtual-tape-library.html

The following are the minimum system requirements

• Multicore/MultiCPU Intel/AMD Processor system
• 8 GB RAM. 64 GB or more recommended for data deduplication
• RHEL/Centos 6.x/7.x, SLES 13 SP3 or Debian 7/8 for x86_64/AMD64 architecture
• QLogic 4Gb/s or above HBA(s) for Fiber Channel connectivity
• 1/10 Gb Ethernet ports for iSCSI connectivity

ip addr add 192.168.1.75/24 dev enp0s3
ip route add default via 192.168.1.1 dev enp0s3
# yum update
# yum install dkms gcc make kernel-devel bzip2 binutils patch libgomp glibc-headers glibc-devel kernel-headers
# mkdir -p /media/cdrom
# mount /dev/cdrom /media/cdrom
# sh /media/cdrom/VBoxLinuxAdditions.run
rpm -q kernel
rpm -q kernel-devel
Make sure they are the same version.  Remote to start using the newest version.
  Confirm you are using newest version using uname -a.
Then rpm -e the old kernel version.
yum install httpd
yum install sg3_utils
yum install policycoreutils-python
gcc, perl kernel-devel were already installed.
/sbin/chkconfig --add httpd (RHEL/CentOS)
sudo systemctl enable httpd.service
sudo systemctl restart httpd.service

yum install sssd realmd oddjob oddjob-mkhomedir adcli samba-common samba-common-tools krb5-workstation openldap-clients policycoreutils-python -y
/usr/sbin/setsebool -P httpd_enable_cgi 1
/usr/sbin/semanage permissive -a httpd_t
sudo firewall-cmd --add-service=http --permanent && sudo firewall-cmd --add-service=https --permanent
sudo systemctl restart firewalld
/etc/init.d/quadstorvtl start

Redhat 7 root password recovery

This is really a note for myself... since it is so terse with no pictures, but may be helpful to someone else. At the boot menu press "e" to edit the boot option find the vmlinuz line and after the root= entry find the ro entry and prior to this enter rw init=sysroot/bin/sh Press Control X and after it boots in single user mode... type chroot /sysroot passwd root passwd mount -o remount / touch /.autorelabel

HPUX NTP setup

/etc/hosts
192.168.1.4. ntp1
192.168.1.5  ntp2

/etc/ntp.conf
server 127.127.1.0  #Local clock
fudge 127.127.1.0 stratum 10

server ntp1 prefer
server ntp2

/etc/rc.config.d/netdaemons
export NTPDATE_SERVER=ntp1
export XNTPD=1
export XNTPD_ARGS="-l /var/adm/xntpd.log"

NTP Pool as alternate external NTP if ports are open:  north-america.pool.ntp.org

My recommendation is for NTP entries to be in DNS as cname records and then just reference the cname records in your configuration files... so if you ever need to change the NTP server you do not have to edit hundreds of client NTP client files.  Just update the DNS entries for NTP1 NTP2 etc.

The reason you update /etc/ntp.conf as well as ntpdate in the netdaemons file... is that ntpdate is intended for a single use on boot up... then from that point on... it gets updated from xntpd running from the /etc/ntp.conf configuration.  The reason for this is that xntpd will refuse to start if the local clock is off by more than 1000 seconds off from the NTP server you wish you get time from and if this happens the xntpd won't start and time will be way off until someone notices... manually runs ntpdate and then starts xntpd again.  Be careful not to cause your clock to go backwards or jump ahead after a database or application is running if it is sensitive to time.  Be sure to read about setting the options to SLEW the clock if you have things like a database running when you need to affect a large time change.