TransportNodeCollectionState

Realization state of attaching or detaching Transport node profile on compute collection.

JSON Example

{
    "aggregate_progress_percentage": 0,
    "cluster_level_error": "string",
    "state": "string",
    "state_detail": "string",
    "validation_errors": [
        {
            "discovered_node_id": "string",
            "error_message": "string"
        }
    ],
    "vlcm_transition_error": "string"
}

integer As int64 As int64

aggregate_progress_percentage

Optional

Average of all transport node deployment progress in a cluster. Applicable only if transport node profile is applied on a cluster.

string

cluster_level_error

Optional

Errors while applying transport node profile which need cluster level action to resolve

string

state

Optional

If the host preparation or transport node creation is going on for any host then state will be "IN_PROGRESS".

If setting desired state of the transport node failed for any of the host then state will be "FAILED_TO_CREATE"

If realization of transport node failed for any of the host then state will be "FAILED_TO_REALIZE"

If Transport node is successfully created for all of the hosts in compute collection then state will be "SUCCESS"

You can override the configuration for one or more hosts in the compute collection by update TN(transport node) request on individual TN. If TN is successfully created for all hosts in compute collection and one or more hosts have overridden configuration then transport node collection state will be "PROFILE_MISMATCH".

The installations triggered via VC import to VCF and Quick Start will support the following additional states:

TZ_CREATE - When the install activity is reading VDS inventory from vCenter and creating corresponding VLAN transport zone objects

TNP_CREATE - When the install activity is creating transport-node-profile based on the VDS to ESX host membership for a given cluster

SEG_SYNC - This indicates that NSX is reading all DVPortgroup inventory associated with the vCenter cluster and creating the corresponding discovered segments.

This state depends on the transport node states. If any update is done (e.g. update transport node profile attached to a cluster, update another transport node profile on a cluster), then transport node collection state might still show same state as before(e.g. SUCCESS if all transport nodes are in SUCCESS state before) until the transport node realization gets started.

Possible values are : FAILED_TO_CREATE, FAILED_TO_REALIZE, IN_PROGRESS, PROFILE_MISMATCH, SUCCESS, TZ_CREATE, TNP_CREATE, SEG_SYNC,

string

state_detail

Optional

Detailed information about the current state of the installation

array of ValidationError

validation_errors

Optional

Transport node profile(TNP) will not be applied to a discovered node(DN) if some validations are not passed. In this case transport node is not created or existing transport node is not updated with TNP configurations.

string

vlcm_transition_error

Optional

When vLCM is enabled on a compute collection in vSphere the transition workflow is triggered. This field indicates error in this special case.

Returned By

Get Transport Node Collection State