Problem deploying Tanzu supervisor services using NSX - Supervisor network eth1 connection failure

Products

• VMware NSX
• VMware Tanzu Kubernetes Grid

Issue/Introduction

 

Supervisor Cluster deploys only the first node with the following warning: 

Waiting for control plane to pass preflight checks to continue reconciliation: Machine ####-#### does not have a corresponding Node yet (Machine.status.nodeRef not set)

Unable to retrieve kubeadm Configmap from the guest cluster: failed to get server groups: Get "https://##.##.##.##:6443/api?timeout=10s": dial tcp ##.##.##.##:6443: connect: connection refused,Addon KubeProxy is not ready: unable to retrieve kube-proxy daemonset from the guest cluster: failed to get server groups: Get "https://##.##.##.##:6443/api?timeout=10s": dial tcp ##.##.##.##:6443: connect: connection refused 

 

Test from the workload network failed from SVM : 

curl -k --interface eth1 https://projects.packages.broadcom.com:443 ; echo $?
curl: (7) Failed to connect to projects.packages.broadcom.com port 443 after 8129 ms: Could not connect to server

 

ESXi host where SVM resides reported tunnels down to Edge nodes:

Environment

VMware Tanzu Kubernetes Grid

VMware NSX

Cause

BFD tunnel down between the ESXi host and the Edge caused SVM Northbound traffic drops.

Resolution

Refer to this article to troubleshoot NSX TEP/BFD Tunnels between ESXi hosts and Edges

https://knowledge.broadcom.com/external/article/379112/troubleshooting-nsx-tepbfd-tunnels-betwe.html

 

Additional Information

Supervisor network requirement:

https://knowledge.broadcom.com/external/article/410597/networking-requirements-for-downloading.html