Computes
nsxt
vio
operation_manager (optional)
log_insight (optional)
- vcenter
management
resource
pods
orchestrator (optional)
The following tables describe the fields in the
nsxt
:
Parameters | Description |
---|---|
ip |
There are 3 controllers. Enter the available IPV4 address from the VM_MGMT network for each of the controllers. |
hostname |
There are 3 controllers. Enter the hostname for each of the controllers. The TICG tool will append the domain name with the hostname. This FQDN should be resolvable from the DNS. |
ctrl_password |
Enter a valid password for NSX-T controller VMs.
NOTE:
The password must conform to following conventions:
|
Parameters | Description |
---|---|
hostname |
Enter the hostname for NSX manager. The TICG tool will append the domain name with the hostname. This FQDN should be resolvable from the DNS. |
ip |
Enter the available IPv4 address from VM_MGMT network. |
password |
Enter a valid password for NSX-T controller VMs.
NOTE:
The password must conform to following conventions:
|
Parameters | Description |
---|---|
edgevm_password |
Enter a valid password for NSX-T EDGE VMs.
NOTE:
The password must conform to following conventions:
|
ip |
Enter the available IPv4 address from VM_MGMT network. |
hostname |
Enter the hostname for NSX-T EDGE VMs. The TICG tool will append the domain name with the hostname. This FQDN should be resolvable from DNS. NOTE:
Ensure that the hostname is entered in all 3 nodes. |
Parameters | Description |
---|---|
overlay_start_address |
Enter the overlay start address for edge_resource ESXI nodes. |
overlay_end_address |
Enter the overlay end address for edge_resource ESXI nodes. |
ext_uplink_ip |
Enter the IPv4 address from External network. |
ip : Enter the available IPv4 address from VM_MGMT network.
|
Parameters | Description |
---|---|
ip |
Enter the available IPv4 address from VM_MGMT network. |
hostname |
Enter the hostname for VIO Manager. The TICG tool will append the domain name with the hostname. This FQDN should be resolvable from the DNS. |
password |
Enter a valid password for VIO appliance. This password is used during SSH to VIO console.
NOTE:
The password must conform to following conventions:
|
vm_mgmt_start_address |
Enter the IPv4 start address from VM_MGMT network. |
vm_mgmt_end_address |
Enter the IPv4 end address from VM_MGMT network.
NOTE:
Minimum 11 consecutive IPv4 addresses must be provided. |
api_start_address |
Enter the IPv4 start address from API network. |
api_end_address |
Enter the IPv4 end address from API network.
NOTE:
Minimum 3 consecutive IPv4 addresses should be provided. |
admin_project_name |
Enter the name of admin project to be created on OpenStack cloud. |
admin_username |
Enter the username for admin project. |
admin_password |
Enter the password for admin user.
NOTE:
The password must conform to following conventions:
|
public_hostname |
Enter valid hostname for OpenStack identity services. This should resolve "public_vip" |
public_vip |
Enter the IPv4 address from API network |
Parameters | Description |
---|---|
password |
Enter a valid password for Operation Manager appliance VM. This password is used during SSH to OMS console.
NOTE:
The password must conform to following conventions:
|
hostname |
Enter the hostname of vRealize Operation Manager Virtual Appliance master node. This should have DNS entry and resolve to master node IP address. |
ip |
Enter the IPv4 address from VM_MGMT network. |
role |
Enter "master" as the Role. |
hostname |
Enter the hostname of vRealize Operation Manager Virtual Appliance replica node. This should have DNS entry and resolve to 'replica' node IP address. |
ip |
Enter the IPv4 address from VM_MGMT network. |
role |
Enter "replica" as the Role. |
hostname |
Enter the hostname of vRealize Operation Manager Virtual Appliance data node. This should have DNS entry and resolve to 'data' node IP address. |
ip |
Enter the IPv4 address from VM_MGMT network. |
role |
Enter "data" as the Role. |
Parameters | Description |
---|---|
password |
Enter a valid password for vRealize Log Insight appliance VM.
NOTE:
The password must conform to following conventions:
|
hostname |
Enter the hostname of vRealize Log Insight master node. This should have DNS entry and must resolve to 'master' node's IP address. |
ip |
Enter the IPv4 address from VM_MGMT network. |
role |
Enter "master" as the Role. |
hostname |
Enter the hostname of vRealize Log Insight worker-1 node. This should have DNS entry and must resolve to 'worker-1' node's IP address. |
ip |
Enter the IPv4 address from VM_MGMT network. |
role |
Enter "worker" as the Role. |
hostname |
Enter the hostname of vRealize Log Insight worker-2 node. This should have DNS entry and must resolve to 'worker-2' node's IP address. |
ip |
Enter the IPv4 address from VM_MGMT network. |
role |
Enter "worker" as the Role. |
Parameters | Description |
---|---|
management | |
hostname |
Enter the hostname of Management vCenter server appliance node. This should have DNS entry and must resolve to its static IP address. |
username |
Enter the username as admin. |
ip |
Enter the IPv4 address from VM_MGMT network. |
password |
Enter a valid password for Management vCenter server.
NOTE:
The password must conform to following conventions:
|
active_ip |
Enter the IPv4 from VCENTER_HA network. This IP will be assigned to secondary vNIC of active Management vCenter server. |
passive_ip |
Enter the IPv4 from VCENTER_HA network. This IP will be assigned to secondary vNIC of passive Management vCenter server. |
witness_ip |
Enter available IPv4 from VCENTER_HA network. This IP will be assigned to secondary vNIC of witness Management vCenter server. |
resource | |
hostname |
Enter the hostname of the Resource vCenter server appliance node. This should have DNS entry and must resolve to its static IP address. |
ip |
Enter the IPv4 address from VM_MGMT network. |
username |
Enter the username as admin. |
password |
Enter a valid password for Management vCenter server.
NOTE:
The password must conform to following conventions:
|
active_ip |
Available IPv4 from VCENTER_HA network. This IP will be assigned to secondary vNIC of active Resource vCenter server. |
passive_ip |
Available IPv4 from VCENTER_HA network. This IP will be assigned to secondary vNIC of passive Resource vCenter server. |
witness_ip |
Available IPv4 from VCENTER_HA network. This IP will be assigned to secondary vNIC of witness Resource vCenter server. |
Parameters | Description |
---|---|
type |
Enter the Pod type for Management. |
name |
Enter name of management POD. Same name must be tagged as role for servers, which are intended to be part of this Pod, in 'servers' section. |
profile |
Profile must be NA for Management Pod. |
storage |
Enter storage backend type. Only 'vsan' storage is supported for this release |
type |
Pod type for edge_resource. |
name |
Enter name of management POD. Same name must be tagged as role for servers, which are intended to be part of this Pod, in 'servers' section. |
profile |
Profile must be "NVDSE". This makes sure that appropriate configuration settings are done on all ESXi nodes whose role matches with pod name. |
storage |
Storage backend type. Only 'vsan' storage is supported in this release. |
Parameters | Description |
---|---|
password |
Enter a valid password for vRealize orchestrator appliance VM.
NOTE:
The password must conform to following conventions:
|
ip |
Enter the IPv4 address from VM_MGMT network. |
hostname |
Enter the hostname of vRealize orchestrator master node. This should have DNS entry and must resolve to its static IP address. |
role |
Enter "master" as the Role. |
ip |
Enter the IPv4 address from VM_MGMT network. |
hostname |
Enter the hostname of vRealize orchestrator replica node. This should have DNS entry and must resolve to its static IP address. . Hostname part of FQDN will be used as VM name. |
role |
Enter "replica" as the Role. |
After the Input JSON file is configured with the required parameter values, save the file to a preferred location. You can validate the Input JSON file using HPE Telco Infrastructure Configuration Generator.