VMware Cloud Foundation VxRail Add secondary cluster workflow fails due to the presence of more than 1000 logical segments
search cancel

VMware Cloud Foundation VxRail Add secondary cluster workflow fails due to the presence of more than 1000 logical segments

book

Article ID: 313881

calendar_today

Updated On:

Products

VMware Cloud Foundation

Issue/Introduction

Symptoms:
VxRail Add Secondary Cluster fails at task 'CreateTransportNodeProfileForAddSecondaryClustertask': failed due to Unable to find logical router.

Log file: /var/log/vmware/vcf/domainmanager/domainmanager.log

Environment

VMware Cloud Foundation 3.10.2.2
VMware Cloud Foundation 3.x
VMware Cloud Foundation 3.10.2.1
VMware Cloud Foundation 3.10.1.2

Cause

This is an NSX-T API Pagination issue. Due to the presence of more than 1000 Logical segments, the required logical segment cannot be fetched as it does not come up in the first 1000 entries fetched by the NSX-T API

Resolution

Currently there is no resolution. 

This issue will be fixed in VCF versions 3.10.2.2 & 3.11.x.x.

For more information about VCF Build Numbers, see Correlating VMware Cloud Foundation version with the versions of its constituent products (52520)

Workaround:
To workaround this issue, please follow the below steps:
  1. Get current workflow context into spec.json.
  1. Backup spec.json.
cp spec.json spec-bk.json
  1. Update spec.json.
 --->Look for element with "vmkernelInterfaceToSegmentsMap"
 Change it from:
 "vmkernelInterfaceToSegmentsMap":{
                    "vmk4":"ls-aea17f68-3079-356f-a401-3efe6c8f2fe4-bb38936b0d73",
                    "vmk3":"ls-b310557d-d81d-323b-a473-e8854d8f3294-bb38936b0d73",
                    "vmk2":"ls-99bd09d7-14b8-3823-9ac2-55745bf53ccc-bb38936b0d73",
                    "vmk0":"ls-87f5531d-d32a-319b-a156-6963cafce1cc-bb38936b0d73"
 }
 To:
 "vmkernelInterfaceToSegmentsMap":{
 }
  1. Check json validity.
 cat spec.json | json_pp
  1. Update spec.json with following command.
curl -s http://localhost:7200/domainmanager/internal/vault/a5a58419-c202-4048-aa39-0aa740c48b39 -XPUT -H "Content-type: text/plain" -d @spec.json
  1. Retry workflow.