SSP Inventory Import Fails with “Parent scope region/zone is not set” When Only Environment is Provided

Products

• VMware vDefend Firewall with Advanced Threat Prevention
• VMware vDefend Firewall

Issue/Introduction

During SSP inventory import, users may encounter validation errors related to missing parent scopes when defining assets with only the environment field populated while leaving region and zone blank.


Symptoms

• Inventory import fails with errors such as:

Parent scope region is not set for child scope zone 
Parent scope zone is not set for child scope environment

• Errors repeat for multiple assets in the annotated Excel output

• Region and Zone fields are left blank in the import file
  
  
• Sample annotated excel looks like 
  
  

Environment

SSP : 5.1 , 5.1.1

Cause

SSP enforces a hierarchical scope model:
Region → Zone → Environment

Although region and zone are not explicitly marked as mandatory in the import template, they become implicitly required when a dependent scope (environment) is provided.

 

Providing only:
environment = any value like prod/dev/test etc
without defining zone and region violates the hierarchy, resulting in validation failure.

 

Resolution

Below workarounds can be used to mitigate this :

Option 1
Provide valid values for region and zone:
region = <value>
zone = <value>

Option 2
Remove the region and zone columns entirely from the Excel file if they are not being used.