NSX Cluster Preparation fails with the error "The uplink name Uplink # is not found in the [Uplink #, Uplink #] list of UplinkHostSwitchProfile"
search cancel

NSX Cluster Preparation fails with the error "The uplink name Uplink # is not found in the [Uplink #, Uplink #] list of UplinkHostSwitchProfile"

book

Article ID: 387732

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Cluster preparation is not complete and each ESXi host shows the following message:
8217: The uplink name Uplink # is not found in the [Uplink #, Uplink #] list of UplinkHostSwitchProfile BaseHostSwitchProfile/########-########-####-########
  • It is possible to see a discrepancy between Uplink and VdsUplink count in the following log file found in /var/log/proton/nsxapi.log: 
    INFO providerTaskExecutor-130 L2TransportNodeProviderHelper 70621 POLICY [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Loaded Host TransportNode proxy HostTransportNode{TransportNodeConfig= TransportNodeConfig{hostSwitch= [HostSwitch [ name = Switch_Name, profiles = [HostSwitchProfileTypeIdEntry [UPLINK/########-####-####-####-############]], pnics = [], migratePnics = false, staticIpPoolId = null, staticIpSpec = null, staticIpMacListSpec = null, ipAssignmentType = DHCP, hostSwitchMode = STANDARD, vmkInstallMigration = null, vmkUninstallMigration = null, pnicsUninstallMigration = null, hostSwitchId = ## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##, hostSwitchType = VDS, transportZoneEndpoints = [TransportZoneEndpoint [transportZoneId=TransportZone/########-####-####-####-############]], uplinks = [VdsUplink{vdsUplinkName='Uplink 1', uplinkName='Uplink 1' vdsLagName='null'}, VdsUplink{vdsUplinkName='Uplink 2', uplinkName='Uplink 2' vdsLagName='null'}, VdsUplink{vdsUplinkName='Uplink 3', uplinkName='Uplink 3' vdsLagName='null'}, VdsUplink{vdsUplinkName='Uplink 4', uplinkName='Uplink 4' vdsLagName='null'}, VdsUplink{vdsUplinkName='Uplink 5', uplinkName='Uplink 5' vdsLagName='null'}, VdsUplink{vdsUplinkName='Uplink 6', uplinkName='Uplink 6' vdsLagName='null'}, VdsUplink{vdsUplinkName='Uplink 7', uplinkName='Uplink 7' vdsLagName='null'}, VdsUplink{vdsUplinkName='Uplink 8', uplinkName='Uplink 8' vdsLagName='null'}], notReady = false, portgroupTransportZoneId = ########-####-####-####-############]], nodeType=ESX, clientId=null, maintenanceMode=DISABLED, migrationParameters=null, ipAddress=[192.168.0.10], transportZoneEndPoints=[TransportZoneEndpoint [transportZoneId=TransportZone/########-####-####-####-############]], markedForDeletion=false, hostSwitchTypeChanged=false, esxMgmtIfMigrationSpecList=null, TnContext=null} , ExternalId=########-####-####-####-############, HardwareId=null, OsType=ESXI, InstallLocation=null, isManualPrep=false, TransportNodeUpdateParameters=null {[policyPath=/infra/sites/default/enforcement-points/default/host-transport-nodes/Transportnode_ID, markedForDelete=false]}, isTnpConfigOverridden=false}  with /infra/sites/default/enforcement-points/default/host-transport-nodes/Transportnode_ID

Environment

VMWare NSX

Cause

The issue occurs due to a discrepancy between the number of uplinks in the "Transport Node Profile" and the "Uplink Host Switch Profile" 

Resolution

  • Check if there are discrepancies between the profiles:

 

    1. GET https://localhost/api/v1/infra/host-switch-profiles/ID
      {
        "teaming" : {
          "policy" : "LOADBALANCE_SRCID",
          "active_list" : [ {
            "uplink_name" : "Uplink 1",
            "uplink_type" : "PNIC"
          }, {
            "uplink_name" : "Uplink 2",
            "uplink_type" : "PNIC"
          } ],
          "rolling_order" : false
        },


    2. GET https://localhost/api/v1/infra/host-transport-node-profiles/ID
      {
        "host_switch_spec" : {
          ...
            } ],
            "uplinks" : [ {
              "vds_uplink_name" : "Uplink 1",
              "uplink_name" : "Uplink 1"
            }, {
              "vds_uplink_name" : "Uplink 2",
              "uplink_name" : "Uplink 2"
            }, {
              "vds_uplink_name" : "Uplink 3",
              "uplink_name" : "Uplink 3"
            }, {
              "vds_uplink_name" : "Uplink 4",
              "uplink_name" : "Uplink 4"
            }, {
              "vds_uplink_name" : "Uplink 5",
              "uplink_name" : "Uplink 5"
            }, {
              "vds_uplink_name" : "Uplink 6",
              "uplink_name" : "Uplink 6"
            }, {
              "vds_uplink_name" : "Uplink 7",
              "uplink_name" : "Uplink 7"
            }, {
              "vds_uplink_name" : "Uplink 8",
              "uplink_name" : "Uplink 8"
            } ],
            "is_migrate_pnics" : false,
            "ip_assignment_spec" : {
              "resource_type" : "AssignedByDhcp"
            },
      ...

  • Make sure that the number of the uplinks in the "Uplink Host Switch Profile" matches the "Transport Node Profile"
  • It may be necessary to increase the number of uplinks in the "Uplink Host Switch Profile" to match the uplink numbers between profiles. If that is the case do the following:
    1. Go to System > Fabric > Profiles > Uplink Profiles
    2. Find the profile that is required to be edited and click on "3 dots" and "Edit"
    3. Click on "Teamings" number
    4. Click on "Add Teaming" and input the details to create the new uplink
Powered by Wolken Software