NSX-T 3.1 API call to Deploy a cluster node VM for NSX-T -node2

[YDN66]

Dear All,

Attempt on the below API call is to deploy 2nd NSX-T manager to deploy and add to cluster, However post man refers to error at line no #40 "Error :Bad String". Post man respond failure.

Experiencing issues with the API Call referenced in https://code.vmware.com/apis/1083/nsx-t  

POST https://192.xxx.xx.xx/api/v1/cluster/nodes/deployments

{
"deployment_requests": [
{
"roles": ["CONTROLLER", "MANAGER"],
"form_factor": "SMALL",
"user_settings":
{
"cli_password": "VMware1!VMware1!",
"root_password": "VMware1!VMware1!"
},
"deployment_config": {
"placement_type": "VsphereClusterNodeVMDeploymentConfig",
"vc_id": "89302963-c484-420e-b9b3-d01a63063d58",
"management_network_id": "dvportgroup-27",
"hostname": "nsxmgr",
"compute_id": "domain-s7",
"storage_id": "datastore-29",
"default_gateway_addresses":[
"192.168.30.1"
],
"management_port_subnets":[
{
"ip_addresses":[
"192.168.30.36"
],
"prefix_length":24
}
],
"dns_servers": [
"192.168.30.30"
]
}
},
{
"roles": ["CONTROLLER", "MANAGER"],
"form_factor": "MEDIUM",
"user_settings": {
"cli_password": "VMware1!VMware1!",
"root_password": "VMware1!VMware1!",
},
"deployment_config": {
"placement_type": "VsphereClusterNodeVMDeploymentConfig",
"vc_id": "89302963-c484-420e-b9b3-d01a63063d58",
"management_network_id": "dvportgroup-27",
"hostname": "nsxtmgr2",
"compute_id": "domain-s7",
"storage_id": "datastore-29",
"default_gateway_addresses":[
"192.168.30.1"
],
"management_port_subnets":[
{
"ip_addresses":[
"192.168.30.39"
],
"prefix_length":24
}
],
"dns_servers": [
"192.168.30.30"
]
}
}
]
}

__________________________________________________________________________________

Refer - 

System Administration > Configuration > NSX Managers > Clusters > Cluster Node Deployments Deploy and register a cluster node VM POST /api/v1/cluster/nodes/deployments

Appreciate experts to help and find the issue or an entire new way of looking into it.

Regards

[shank89 · Accepted solution]

Hi @YDN66 

The below should work for you (it did for me).  Just make sure you enter the right details for your environment.

{
	"deployment_requests": [{
			"roles": ["CONTROLLER", "MANAGER"],
			"form_factor": "MEDIUM",
			"user_settings": {
				"cli_password": "ComplexPassword",
				"root_password": "ComplexPassword"
			},
			"deployment_config": {
				"placement_type": "VsphereClusterNodeVMDeploymentConfig",
				"vc_id": "69874c95-51ed-4775-bba8-e0d13bdb4fed",
				"management_network_id": "management_63",
				"hostname": "mgr2",
				"compute_id": "domain-s9",
				"storage_id": "datastore-12",
				"default_gateway_addresses": [
					"192.168.63.1"
				],
				"management_port_subnets": [{
					"ip_addresses": [
						"192.168.63.99"
					],
					"prefix_length": 22
				}],
				"dns_servers": [
					"192.168.63.101"
				]
			}
		},
		{
			"roles": ["CONTROLLER", "MANAGER"],
			"form_factor": "MEDIUM",
			"user_settings": {
				"cli_password": "ComplexPassword",
				"root_password": "ComplexPassword"
			},
			"deployment_config": {
				"placement_type": "VsphereClusterNodeVMDeploymentConfig",
				"vc_id": "69874c95-51ed-4775-bba8-e0d13bdb4fed",
				"management_network_id": "network-13",
				"hostname": "node-1",
				"compute_id": "domain-s9",
				"storage_id": "datastore-12",
				"default_gateway_addresses": [
					"192.168.63.1"
				],
				"management_port_subnets": [{
					"ip_addresses": [
						"192.168.63.56"
					],
					"prefix_length": 24
				}],
				"dns_servers": [
					"192.168.63.101"
				]
			}
		}
	]
}

[YDN66 · Accepted solution]

Hi Shashank Mohan,

Absolutely worked! Thank you for your research.

[YDN66]

Thank you for sharing. Great work,

[YDN66]

Dear Experts,

The deployment of additional NSX-T nodes went fine went fine however at the end "Installation Failed" reported on NSX-T>System>Appliances.VM is online on vCenter. IP configurations(IP/subnet/mask) are correct.NSX-T nodes are able to ping each other.

Reason mentioned :The cluster node VM failed to register itself with the MP within the allotted wait time

 Appreciating help! 

[shank89]

Time to dig into some log files to see what the issue was.  It sounds like it timed out before it was able to join for whatever reason.

Hard to tell without any more info.