vDefend License Hub: SSP Deployment Fails with DNS or IP Pool Reservation Errors
search cancel

vDefend License Hub: SSP Deployment Fails with DNS or IP Pool Reservation Errors

book

Article ID: 450331

calendar_today

Updated On:

Products

VMware vDefend Firewall

Issue/Introduction

During License Hub deployment, the installer pre-check fails with a DNS or IP pool reservation error.

Error 1: NodePool IP count is insufficient: required at least 4, but only 3 found.. 
Error 2: ServicePool IP count is insufficient: required at least 4, but only 2 found.. 
Error 3: invalid sspi ip 10.#.#.# overlaps with [10.#.#.# - 10.#.#.#].

A common variant reports that License Hub IP falls incorrectly within a configured range, even when FQDN assignments follow standard setup guidance.

Example:

Environment

  • VMware vDefend License Hub 5.1.2
  • VMware Cloud Foundation (VCF) 9.1

 

Cause

The pre-check fails under either of these conditions:

  • The Node Pool or Service Pool contains fewer than the required minimum of 4 IPs.
  • Forward and reverse DNS lookups for the Instance (SSP) and Messaging FQDNs do not resolve to the first and second IPs of the Service Pool.
  • The SSP Installer (SSPI) IP is included in the Service Pool or Node Pool range.

Resolution

  1. Exclude the SSPI IP from all pools. The SSPI VM's IP address must not fall within the Service Pool or Node Pool ranges.
  2. Configure the Service Pool. Allocate at least 4 IPs. Assign the Instance FQDN to the first IP in the range and the Messaging FQDN to the second; the installer pre-check issues a warning if this is not configured. Example: Service Pool 10.#.#.1 – 10.#.#.4, where Instance FQDN = 10.#.#.1 and Messaging FQDN = 10.#.#.2.
  3. Configure the Node Pool. Reserve a separate range of at least 4 IPs for the controller and worker nodes.