Override NSX-T Ownership Constraints

When a transport node profile (TNP) is applied to a cluster if any validations (VMs are running on hosts) fail then Transport Node is not created. After ensuring validations pass, you can reapply cluster configuration using API. However, if you want the node to give up ownership of its managed objects you can call the override_nsx_ownership parameter in the API call.

You must only override ownership of managed objects from a NSX-T instance if any one of the following condition is true:

• NSX-T instance is not responding or unusable

• NSX-T is no longer actively managing its objects

Caution: If the managed objects affected by this operation are actively used by the NSX-T that owns these objects, then it could corrupt host switch configurations that are pushed down by the NSX-T instance.

Prerequisites

Procedure

• ♦ Call the following API to override NSX-T ownership constraints.
  POST https://<nsx-mgr>/api/v1/fabric/discovered-nodes/5c669dc6-47a8-4508-3077-6a48f26c5a4g?action=reapply_cluster_config&override_nsx_ownership=true

  Where, override_nsx_ownership=true when set to True overrides NSX-T ownership of managed objects.

  However, it is not recommended to pass this parameter. If you use this parameter it indicates you want to own certain managed objects owned by another NSX instance.

  {
    "resource_type": "TransportNode",
    "description": "Updated NSX configured Test Transport Node",
    "id": "77816de2-39c3-436c-b891-54d31f580961",
    "display_name": "NSX Configured TN",
    "host_switch_spec": {
      "resource_type": "StandardHostSwitchSpec",
      "host_switches": [
        {
          "host_switch_profile_ids": [
            {
              "value": "e331116d-f59e-4004-8cfd-c577aefe563a",
              "key": "UplinkHostSwitchProfile"
            },
            {
              "value": "9e0b4d2d-d155-4b4b-8947-fbfe5b79f7cb",
              "key": "LldpHostSwitchProfile"
            }
          ],
          "host_switch_name": "nsxvswitch",
          "pnics": [
            {
              "device_name": "vmnic1",
              "uplink_name": "uplink1"
            }
          ],
          "ip_assignment_spec": {
            "resource_type": "StaticIpPoolSpec",
            "ip_pool_id": "ecddcdde-4dc5-4026-ad4f-8857995d4c92"
          },
          "vmknics": [
            {
              "device_name": "vmk1",
              "logical_switch_id": "849e339e-64b7-47cb-9480-33068f70dc5a"
            }
          ]
        }
      ]
    },
    "transport_zone_endpoints": [
      {
        "transport_zone_id": "e14c6b8a-9edd-489f-b624-f9ef12afbd8f",
        "transport_zone_profile_ids": []
      }
    ],
    "node_id": "41a4eebd-d6b9-11e6-b722-875041b9955d",
    "node_deployment_info": {
      "resource_type": "HostNode",
      "id": "41a4eebd-d6b9-11e6-b722-875041b9955d",
      "display_name": "FN1",
      "fqdn": "sc2-rdops-vm03-dhcp-110-133.eng.vmware.com",
      "ip_addresses": [
        "10.192.156.199"
      ],
      "external_id": "a5113680-6a56-4386-9017-adffbe56c99e",
      "discovered_ip_addresses": [],
      "os_type": "ESXI",
      "os_version": "",
      "managed_by_server": "",
      "_create_time": 1538632396987,
      "_last_modified_user": "admin",
      "_protection": "NOT_PROTECTED",
      "_last_modified_time": 1538632396987,
      "_create_user": "admin",
      "_revision": 0
    },
    "_create_time": 1485299990773,
    "_last_modified_user": "admin",
    "_last_modified_time": 1485301913130,
    "_create_user": "admin",
    "_revision": 0
  }

  NSX-T no longer owns managed objects. These objects can be now owned by another NSX-T instance.