The Fabric Services System deployer VM

The procedures in this section describe how to deploy and configure the Fabric Services System deployer VM.

Downloading the Fabric Services System deployer image

Contact Nokia support for the location of the Fabric Services System deployer image (OVA or QCOW2).
Table 1. Deployer VM images
Deployment Where to download the image
VMware vSphere Download the OVA image to a host that can reach the VMware vCenter or ESXi host on which it will be deployed.
KVM Download the QCOW2 image to the deployer host.

Prepare the Fabric Services System deployer hypervisor

Before you install the deployer VM, you must prepare the node on which you are installing the deployer VM. Virtualization must be enabled on the node, and can be enabled in the BIOS/EFI. You must also install a VMware vSphere or KVM environment on the node before installing the deployer VM.

Configuring the Fabric Services System deployer VM

  1. From the VMware vSphere console or the KVM console, log in to the deployer VM.

    Use the following credentials:

    Username: root

    Password: N0ki@FSSb4se!

    Note: After the initial login, Nokia recommends that you change this default password to a stronger password to enhance the security of the deployer and the Fabric Services System environment.
  2. If your environment does not support or use cloud-init services, disable and stop these services. 
    # systemctl stop cloud-init cloud-init-local cloud-config cloud-final
    # systemctl disable cloud-init cloud-init-local cloud-config cloud-final
  3. Enable SSH.
    The base image is a hardened image so SSH is disabled by default for the root user. To enable SSH, update the /etc/ssh/sshd_config file and change the following lines:
    PasswordAuthentication no
PermitRootLogin no
    to:
    PasswordAuthentication yes
PermitRootLogin yes
    Note: You can keep password authentication disabled to provide extra security. In this case, only key-based authentication works, and you must configure the appropriate public SSH keys for the root user so it can log in over SSH. In any case, this configuration is needed for the deployer VM to reach the nodes.
  4. Restart SSH . 
    # systemctl restart sshd
  5. Edit the /etc/sysconfig/network-scripts/ifcfg-eth0 file to configure the correct static IP address, DNS servers, and gateway.
    The final content should look similar to the following, except with the IP address, DNS, and domain details specific to the target environment:
    BOOTPROTO=static
DEVICE=eth0
ONBOOT=yes
TYPE=Ethernet
USERCTL=no
IPADDR=192.0.2.10
PREFIX=24
GATEWAY=192.0.2.1
DNS1=192.0.2.5
DNS2=192.0.2.6
DOMAIN=fss.nokia.local
MTU=9000
  6. Restart the network to apply the new configuration.

    Execute the following command:

    # systemctl restart NetworkManager.service
  7. Configure the appropriate NTP servers.
    Edit the /etc/chrony.conf configuration file and replace all lines beginning with server with the correct server lines for the environment.
  8. Restart the chronyd service. 
    # systemctl restart chronyd
  9. Verify that time synchronization is functioning properly. 
    # chronyc tracking

    If the Reference ID field does not show any of the configured servers, but instead refers to something like 127.127.1.1, time synchronization is not functioning properly.

    Reference ID    : 87E30FFE (192.0.2.5)
Stratum         : 4
Ref time (UTC)  : Wed Feb 16 01:20:36 2022
System time     : 0.000014215 seconds slow of NTP time
Last offset     : -0.000001614 seconds
RMS offset      : 0.000106133 seconds
Frequency       : 11.863 ppm slow
Residual freq   : -0.071 ppm
Skew            : 0.187 ppm
Root delay      : 0.063009784 seconds
Root dispersion : 0.018440660 seconds
Update interval : 64.5 seconds
Leap status     : Normal
  10. Synchronize the RTC clock and the system clock.

    Ensure that the RTC and the system clock are synchronized after every reboot.

    # hwclock --systohc
    Then, verify that local time and the RTC time are synchronized.
    # timedatectl
  11. Optional: Change the hostname. 
    # hostnamectl set-hostname new-hostname.domain.tld
  12. Reboot the Fabric Services System deployer VM to ensure that all services come up with the correct network configuration. 
    # reboot