Prerequisites

Last published : Jun 12, 2026
  1. Be ready with the following information -
    • Names of all the nodes.
      Note: Runoc get nodes -o wideon the bastion node to obtain Names and IP addresses of the nodes.
Use NAME and INTERNAL-IP from the output similar to the following -
NAME                STATUS ROLES  AGE VERSION         INTERNAL-IP
ocp-cp-1.lab.ocp.lan Ready master 54d v1.22.1+d8c4430 192.168.22.201
77.rhaos4.9.gitd745cab.el8
ocp-cp-2.lab.ocp.lan Ready master 54d v1.22.1+d8c4430 192.168.22.202
77.rhaos4.9.gitd745cab.el8
ocp-cp-3.lab.ocp.lan Ready master 54d v1.22.1+d8c4430 192.168.22.203
77.rhaos4.9.gitd745cab.el8
ocp-w-1.lab.ocp.lan Ready worker  54d v1.22.1+d8c4430 192.168.22.211
77.rhaos4.9.gitd745cab.el8
ocp-w-2.lab.ocp.lan Ready worker  54d v1.22.1+d8c4430 192.168.22.212
77.rhaos4.9.gitd745cab.el8
ocp-w-3.lab.ocp.lan Ready worker  54d v1.22.1+d8c4430 192.168.22.213
77.rhaos4.9.gitd745cab.el8
ocp-w-4.lab.ocp.lan Ready worker  54d v1.22.1+d8c4430 192.168.22.214
77.rhaos4.9.gitd745cab.el8
  • Operating system hardware path of the disks which are being managed by other storage vendors that need to be excluded from InfoScale disk group.
  • Optionally if you want to exclude boot disks, device path to the boot disks.
    Note: Veritas recommends excluding boot disks.
  • If you have internet connectivity and download is allowed, you must be logged in to Red Hat registry.
  • For air gapped systems, Custom Registry address to set up registry where InfoScale images are pushed.
  • Fencing controller and fencing enabler pods require access to an external repository. Allow access to the following registry:
Fencing registry - "ghcr.io/kvaps"
  1. Ensure that all nodes are synchronized with the NTP Server.
  2. Reserve network ports for exclusive use of InfoScale as under -
    Component Port
    LLT over UDP Serially onwards 50000 (as many as configured LLT links)
    VVR (Needed only if you want to configure DR) 4145 (UDP), 8199 (TCP), 8989 (TCP)
  3. Add local or shared storage to all the worker nodes before you proceed with the deployment.
  4. Ensure that stale InfoScale kernel modules (vxio,vxdmp,veki,vxspec,vxfs,odm,glm,gms) from previous installation do not exist on any of the worker nodes.
    Note: You can reboot a worker node to unload all stale InfoScale kernel modules.
  5. Hostnames of the InfoScale nodes must exactly match with the fully qualified domain names(FQDN) of the OpenShift nodes.
  6. OpenShift cluster must be configured by using IPv4 only.
  7. Cert-manager v1.11 or later on OCP 4.12 or Cert-manager v1.7.1 on OCP 4.11 (Red Hat-certified) must be installed.
  8. NFD must be installed.