NsxtConfiguration
{
"auto_import_nsx_projects": false,
"automate_dfw_objects": false,
"automate_dfw_rules": false,
"data_network_config": {
"tier1_segment_config": {
"automatic": {
"nsxt_segment_subnet": {
"ip_addr": {
"addr": "string",
"type": "string"
},
"mask": 0
},
"num_se_per_segment": 0,
"tier1_lr_ids": [
"string"
]
},
"manual": {
"tier1_lrs": [
{
"locale_service": "string",
"segment_id": "string",
"tier1_lr_id": "string"
}
]
},
"segment_config_mode": "string"
},
"transport_zone": "string",
"tz_type": "string",
"vlan_segments": [
"string"
]
},
"domain_id": "string",
"enforcementpoint_id": "string",
"management_network_config": {
"overlay_segment": {
"locale_service": "string",
"segment_id": "string",
"tier1_lr_id": "string"
},
"transport_zone": "string",
"tz_type": "string",
"vlan_segment": "string"
},
"nsxt_credentials_ref": "string",
"nsxt_url": "string",
"onboard_avi_into_nsx": false,
"site_id": "string",
"verify_certificate": false,
"vmc_mode": false,
"vpc_mode": false
}Set this flag to true to enable automatic import of NSX projects into Avi.This flag is only applicable when VPC mode is enabled for this cloud; it is ignored when VPC mode is disabled.NSX projects under VCF-A management are excluded from this automatic import process, as VCF-A creates these projects in Avi through its own integration workflow. Field introduced in 32.1.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.
Automatically create/delete DFW objects such as NSGroups and NSServices in NSX-T Manager. Field introduced in 30.2.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.
Automatically create DFW rules for VirtualService in NSX-T Manager. Field introduced in 20.1.1. Allowed with any value in Enterprise, Essentials, Enterprise with Cloud Services edition. Allowed in Basic (Allowed values- false) edition.
Domain where NSGroup objects belongs to. Field introduced in 20.1.1. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.
Enforcement point is where the rules of a policy to apply. Field introduced in 20.1.1. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.
Credentials to access NSX-T manager. It is a reference to an object of type CloudConnectorUser. Field introduced in 20.1.1. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.
NSX-T manager hostname or IP address. URL changes are allowed only between IP and FQDN formats that resolve to the same NSX-T manager. Field introduced in 20.1.1. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.
Enable to automatically register the Avi Controller with NSX-T Manager. This triggers the NSX onboarding workflow API to configure the ALB cluster and create an enforcement point. Note This flag must be enabled on exactly one NSX-T Cloud to avoid conflicts. Field introduced in 32.1.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.
Site where transport zone belongs to. Field introduced in 20.1.1. Allowed with any value in Enterprise, Essentials, Basic, Enterprise with Cloud Services edition.
Flag is used to indicate whether TLS certificate verificationbe done when establishing a connection to a vCenter and NSX-T Manager. Field introduced in 31.1.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.
VMC mode. Field introduced in 30.1.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.
VPC Mode. Field introduced in 30.1.1. Allowed with any value in Enterprise, Enterprise with Cloud Services edition.