Reference Architecture Infrastructure Deployer (RAID) for NFV · 2019-12-18 · Reference...

December 2018 December 2019

Reference Architecture Infrastructure Deployer (RAID) for NFV RAID to deploy NFV 3.2 VCD

Reference Architecture Infrastructure Deployment User Guide

2

VMware, Inc. 3401 Hillview Avenue Palo Alto CA 94304 USA Tel 877-486-9273 Fax 650-427-5001 www.vmware.com

1 Introduction ................................................................................................................ 4

1.1 Audience ............................................................................................................................... 4

2 Requirements ............................................................................................................. 4

2.1 Physical Infrastructure .......................................................................................................... 4

2.2 Software Infrastructure ......................................................................................................... 5

2.3 Supporting Infrastructure ...................................................................................................... 6

3 RAID components ...................................................................................................... 6

3.1 Input file ................................................................................................................................ 7

4 RAID execution workflow .......................................................................................... 7

5 Deployment mode ...................................................................................................... 7

5.1 Full deployment .................................................................................................................... 7

5.2 Custom deployment .............................................................................................................. 8

6 Sample script .............................................................................................................. 9

7 Automation lifecycle ................................................................................................ 10

8 Input file parameters sections................................................................................. 10

8.1 Infrastructure ....................................................................................................................... 11

8.2 Management vCenter Deployment and Configuration ....................................................... 14 8.2.1 Management vCenter Deployment ........................................................................................... 14 8.2.2 Management vCenter Configuration ......................................................................................... 17

8.3 Resource vCenter Deployment and Configuration ............................................................. 23 8.3.1 Resource vCenter Deployment ................................................................................................. 23 8.3.2 Resource vCenter Configuration ............................................................................................... 25

8.4 Edge Cluster Configuration ................................................................................................ 30

8.5 NSX-T Manager Deployment and Configuration ............................................................... 33 8.5.1 NSX-T Manager Deployment .................................................................................................... 33 8.5.2 NSX-T Manager Configuration .................................................................................................. 35 8.5.3 NSX-T Manager components for VCD configuration ................................................................ 36

8.6 vRealize Log Insight Deployment and Configuration ........................................................ 39 8.6.1 vRealize Log Insight Deployment .............................................................................................. 39 8.6.2 vRealize Log Insight Configuration ........................................................................................... 41

8.7 vRealize Operations Manager Deployment and Configuration .......................................... 42


3


8.7.1 vRealize Operations Manager Deployment .............................................................................. 43 8.7.2 vRealize Operations Manager Configuration ............................................................................ 45

8.8 VMware vCloud Director Deployment and Configuration ................................................ 45 8.8.1 VMware vCloud Director Deployment ....................................................................................... 45 8.8.2 VMware vCloud Director Configuration ..................................................................................... 49

8.9 NSX-V Manager Deployment and Configuration .............................................................. 49 8.9.1 NSX-V Manager Deployment .................................................................................................... 49 8.9.2 NSX-V Manager Configuration .................................................................................................. 51

9 General purpose scripts .......................................................................................... 53

10 Functions implementation ..................................................................................... 54

11 Troubleshooting ..................................................................................................... 56

12 Authors list ............................................................................................................. 57


4


1 Introduction

RAID (Reference Architecture Infrastructure Deployer) for NFV is an automation-based deployment tool used for setting up the VMware vCloud® NFV VCD platform, based on the design introduced in the VMware vCloud NFV 3.0 Reference Architecture document. This document details VCD 3.2 and NSX 2.4 deployment and configuration but follows the same Reference Architecture document specified above. RAID is meant for greenfield deployments only. This document introduces the tool and provides usage and other useful information.

1.1 Audience

This document helps users to set up and configure the VMware vCloud NFV VCD platform for testing and implementation.

2 Requirements

This section lists out the physical, software and supporting infrastructure component requirements for RAID.

2.1 Physical Infrastructure

The following table lists the physical infrastructure components required for successful execution of the RAID software. Refer to the VMware vCloud NFV 3.0 Deployment Guide for more details.

Table 1: Physical Infrastructure requirements for RAID

COMPONENT DESCRIPTION

Servers (Physical hosts)

▪ Minimum of 6 hosts for 2-POD and 9 hosts for 3-POD

▪ All servers should be VSAN capable

▪ Each server should have at least 4 physical adapters preferably 10Gbps OR 2 dual-port ethernet controllers, with a total of 4 ethernet ports

▪ An additional host is required to setup the software and supporting infrastructure components. This host does not have to

https://docs.vmware.com/en/VMware-vCloud-NFV/3.0/vmware-vcloud-nfv-30.pdf

https://docs-staging.vmware.com/en/VMware-vCloud-NFV/3.0/vmware-vcloud-nfv-30-deployment.pdf

https://docs-staging.vmware.com/en/VMware-vCloud-NFV/3.0/vmware-vcloud-nfv-30-deployment.pdf


5


conform to the VSAN requirement and can use an NFS datastore instead

Storage

▪ For VSAN, systems should have at least one solid-state drive (SSD) and one or more hard-disk drives (HDDs). All-flash (SSD) configuration is also supported by RAID.

▪ All storage identified for VSAN should be consistent on all hosts, to avoid imbalance errors

Network

▪ Private VLANs in trunked mode should be configured and should be inter-routable for all network adapters.

▪ If the required number of VLANS are not available, some of the networks can share VLANs

2.2 Software Infrastructure

Software components are listed in the following table.

Table 2: Software Infrastructure requirements for RAID


Jump host

A jump host windows VM should be setup on the infrastructure host. RAID is executed on this VM. This VM should have access to all the supporting infrastructure components listed in the table below.

PowerShell Version 5.0 or higher

PowerCLI Version 10.x or higher

VMware and PowerNSX modules

These modules need to be installed on the Jump host.

Important: Windows patches Latest patches should be installed on the jump host for the scripts to run successfully.


6


2.3 Supporting Infrastructure

Supporting infrastructure components are listed in Table 3. These components are typically deployed in the data center network with connectivity to the management network. Deploy these components as virtual machines (VM) to leverage the VMware vSphere High Availability (HA) feature.

Table 3: Supporting Components


Directory Server Provides a centralized authentication source for management components

DNS Server

Provides forward and reverse lookup services to all platform components.

NOTE: All component and physical servers used for deployment should have their FQDN updated in the DNS server. This is a hard requirement for RAID

NTP Server Provides a time synchronization service to all components

SMTP Server Sends email notifications from the platform in response to events and alarms

SNMP Server Sends SNMP alerts to external monitoring systems

3 RAID components

RAID has two major components – the input text file where the user is required to enter all the details of the testbed and products that need to be deployed, and the power shell scripts which do the actual deployment of the products. Details of each one is given below.


7


3.1 Input file

The user input file (InputFile-NFVStack), is a text file for providing user input. All information related to the testbed and products to be deployed are to be populated in this file. 3.2 PowerShell script

The power shell script (Buildout.ps1), is a master script which is used to deploy the entire NFV OSE stack. More details about the script and its components are discussed in the following sections.

4 RAID execution workflow

Follow these steps to download and use RAID

a) Prepare a jump host (see Table 2 above)

b) Download the RAID 3.2 scripts from here - Infrastructure deployer for vCloud NFV

c) Setup the pre-requisites as outlined in the RAID User Guide (this document)

d) Populate the InputFile-NFVStack.txt with information about the testbed, products to be installed etc.

e) Use the buildout.ps1 master script to run a full or custom deployment (detailed below). Run the following powershell commands before starting any script –

Set-ExecutionPolicy unrestricted Unblock-File <folder where RAID scripts are downloaded\*>

5 Deployment mode

There are two modes in which RAID can be deployed.

5.1 Full deployment

In full deployment, all supported products can be deployed by executing the master script, Buildout.ps1, in the power shell console.

NOTE: Buildout.ps1 does not include a script to install ESXi host. It is assumed that the user has already completed a fresh installation of ESXi on the hosts that will be used in the testbed. The RAID package does include a PXE boot script (pxe_boot_servers.ps1) that was used by the validation team. The script has the following prerequisites:

a) Setup a PXE VM with TFTP and DHCP servers installed and configured.

https://flings.vmware.com/infrastructure-deployer-for-vcloud-nfv

https://flings.vmware.com/infrastructure-deployer-for-vcloud-nfv


8


b) Copy the required ESXi boot image to the PXE vm.

c) Create a kickstart file for each server on the PXE vm that has all the input values needed for ESXi installation.

d) Set the boot order on each server to point to the PXE image at first boot.

e) Setup the correct VLAN information in the BIOS for each server.

Follow PXE booting the ESXi Installer, for detailed steps on how to setup the TFTP, DHCP servers and kickstart (ks) files.

5.2 Custom deployment

Individual products can be chosen for deployment by executing the corresponding script or by editing the master script, BuildOut.ps1, retaining the script needed for execution and commenting out the rest. Then, execute the master script in the power shell console as shown in the previous paragraph.

The following product scripts are available for deployment:

▪ Deploy_Management_vCenterServer.ps1 (see Sec 8.2.1)

▪ Deploy_Resource_vCenterServer.ps1 (see Sec 8.3.1)

▪ Deploy_NSXT_Manager.ps1 (see Sec 8.5.1)

▪ Deploy_NSXV_Manager.ps1 (see Sec 8.9.1)

▪ Deploy_vRealizeLogInsight.ps1 (see Sec 8.6.1)

▪ Deploy_vRealizeOperationManager.ps1 (see Sec 8.7.1)

▪ Deploy_vCloud_Director.ps1 (see Sec 8.8.1)

The following product scripts can be used for configuration:

▪ Config_Management_vCenterServer (see Sec 8.2.2)

▪ Config_Resource_vCenterServer (see Sec 8.3.2)

▪ Config_NSX-T_Manager (see Sec 8.5.2)

▪ Config_Resource_NSX-V (see Sec 8.9.2)

▪ Config_vRealize_LogInsight (see Sec 8.6.2)

▪ Config_vRealize_LogInsight_ContentPack

▪ Config_vCloud_Director (see Sec 8.8.2)

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.esxi.install.doc/GUID-B9DB94CA-4857-458B-B6F1-6A688726AED0.html


9


6 Sample script

A sample script which deploys only the management vCenter server is shown below.


10


7 Automation lifecycle Items highlighted in red are not available in this release.

8 Input file parameters sections

The input file is in simple text format, designed to remove dependencies with respect to versions and validations. The input parameters are in a key-value pair format ex: <Key>=<Value>

Start Automation Verfiy

prerequisites(Enviornment etc)

Cleanup the enviornment

Check if management

vCenter server should be deployed

on vSAN

Deploy Management

vCenter server

Configure Managment

vCenter Server

Configure VCHA for

Management vCenter

Deploy NSX-T Manager

Deploy vRealize

LogInsight (Master+2 Workers)

Deploy vRealize

Operation Manager

Deploy VMware

Integrated OpenStack

Deploy vRealize Network Insight

Platform

Deploy Resource vCenter server

Configure Resource vCenter server

Configure VCHA for Resource vCenter

Configure NSX-T

Manager & Controllers

Configure vRealize

LogInsight

Deploy vRealize Network

Insight Proxy

Configure vRealize

Operation Manager


11


The parameters in the input file are grouped into different sections based on the NFV stack. Details of parameters required for each section are listed in the following tables.

8.1 Infrastructure

Infrastructure parameters are the basic testbed and test environment parameters required for deploying any product in the NFV stack.

Prerequisites:

1) The physical, software and supporting infrastructure components are all setup and available.

2) DNS server should have the forward and reverse lookup configured for all products that will be deployed in the testbed.

Table 4: Input values for Infrastructure components

Parameter Name Description Required (Y/N)

Default value

Example

InfraNTPServer NTP server IP or FQDN

Y InfraNTPServer=x.x.x.x

InfraDNSServer DNS server IP Y InfraDNSServer=x.x.x.x

InfraDomain Domain Name Y InfraDomain=example.com

Esxi_Mgmt_Network_Managed_by_VSS

By default, the script will migrate the ESXi management network from VSS to VDS

N N

MgmtHostIp1 IP address or hostname of the 1st management host

Y MgmtHostIp1=x.x.x.x

MgmtHostIp2 IP address or hostname of the 2nd management host



12



Default value

Example

MgmtHostIp3

(Note: More hosts can be added as needed. Continue with MgmtHostIp4 etc.)

IP address or hostname of the 3rd management host


ResHostIp1 IP address or hostname of 1st resource host

Y ResHostIp1=x.x.x.x

ResHostIp2 IP address or hostname of 2nd resource host


ResHostIp3 IP address or hostname of 3rd resource host


EdgeHostIp1 IP address of hostname of 1st Edge host

Y for 3-POD topology

EdgeHostIp1=x.x.x.x

EdgeHostIp2 IP address or hostname of 2nd Edge host


EdgeHostIp2=x.x.x.x

EdgeHostIp3 IP address or hostname of 3rd Edge host


EdgeHostIp3=x.x.x.x

MgmtHostUser Username of the Management ESXi host

Y MgmtHostUser=root

MgmtHostPassword Password of the Management ESXi host

Y MgmtHostPassword=mypassword

ResHostUser Username of the Resource ESXi host

Y ResHostUser=root


13



Default value

Example

ResHostPassword Password of the Resource ESXi host

Y ResHostPassword=mypassword

EdgeHostUser Username of the Edge ESXi host


EdgeHostUser=root

EdgeHostPassword Password of the Edge ESXi password


EdgeHostPassword=mypassword

NFSIp IP address of the NFS server

Y if storage is NFS

NFSIp=x.x.x.x

NFSMountPoint

Mount point of NFS server

NOTE: RAID assumes that a vmkernel adapter is not necessary to mount NFS on the host. If one is needed, user has to manually create a vmkernel adapter on each host before running RAID

Y if storage is NFS

NFSMountPoint=/nfs/share

NFSName NFS name to mount on the ESXi server

Y if storage is NFS

NFSName=TestNFS

MgmtDatastoreType

Datastore type used for Mgmt cluster. Options are vSAN or NFS

Y MgmtDatastoreType=vSAN

ResDatastoreType Datastore type used for Resource

Y ResDatastoreType=vSAN


14



Default value

Example

cluster. Options are vSAN or NFS

EdgeDatastoreType

Datastore type used for Edge cluster. Options are vSAN or NFS


EdgeDatastoreType=vSAN

PODDesign Deployment topology. Options are 2POD or 3POD

Y PODDesign=3POD

8.2 Management vCenter Deployment and Configuration

Management vCenter server will be deployed and configured.

8.2.1 Management vCenter Deployment

Script Name: Deploy_Management_vCenterServer.ps1

▪ Deploys the management vCenter server appliance.

▪ If VSAN is set as storage, a single node VSAN will be created and used for management vCenter server deployment.

Prerequisites:

1) IP addresses and hostnames for the server should be recorded in the DNS server and should be resolvable.

Table 5: Input values for Management vCenter deployment

NOTE: All values are required. Only parameters with default values are optional


15



Default value

Example

vCenterBinaryPath Path to the vCenter ISO

Y

vCenterBianryPath=c

:\\builds\VMware-

VCSA-all-6.7.0-

123456.iso

MgmtVCDeploymentNetwork

Portgroup name on the VSS which will be used to deploy the vCenter appliance

Y

MgmtVCDeployment

Network=MGMT-

VLAN123

MgmtVCDeploymentOption

Management vCenter deployment type. Options are small, medium, large

N small MgmtVCDeployment

Option=medium

MgmtVCApplianceName Management vCenter appliance name

Y MgmtVCApplianceN

ame=MGMT=VC

MgmtVCHostname Management vCenter FQDN

Y MgmtVCHostname=Mgmt01.example.com

MgmtVCName Management hostname

Y MgmtVCName=Mgmt01

MgmtVCGateway

Gateway address to deploy management vCenter

Y MgmtVCGateway=x.x.x.x

MgmtVCSubnetMask

Subnet to deploy management vCenter

Y MgmtVCSubnetMask=x.x.x.x


16



Default value

Example

MgmtVCIpAddress Management vCenter IP address

Y MgmtVCIpAddress=x.x.x.x

MgmtVCIpFamily Management vCenter IP family

N IPv4 MgmtVCIpFamily=IPv4

MgmtVCNetworkMode

Management vCenter mode. Static or Dynamic (Only static accepted for this release)

N static MgmtVCNetworkMode=static

MgmtVCNetworkPrefix Management network prefix

Y MgmtVCNetworkPrefix=24

MgmtVCRootPassword Password for the ‘root’ user

Y

MgmtVCSSOPassword SSO password for management appliance

Y

MgmtVCSSODomain SSO domain for management appliance

Y MgmtVCSSODomain=vsphere.local

MgmtVCUserName

SSO user for the management vCenter

Y [email protected]

MgmtSubNet NetworkID for the IP network profile creation

Y MgmtSubNet=x.x.x.x


17


8.2.2 Management vCenter Configuration

Script Name: Config_Management_vCenterServer.ps1

Configures the management vCenter server.

▪ Create a datacenter, cluster and add hosts

▪ Create infrastructure and tenant virtual distributed switches and adds port groups as per the RA design.

▪ If external NFS is used as the storage and a portgroup and a vmkernel adapter ip address is specified, the script will add a vmkernel adapter for NFS, to the Infra VDS.

▪ The uplink ports for the distributed switches are assigned according to the values given in the input file.

o If the MgmtHostInfraNic and MgmtHostTenantNic values for each host are blank, then the script looks for all the available uplink ports and assigns them in the order in which they were found. The script ONLY looks for 10G ports available. The number of uplink ports is set according to the value set in the parameters -

MgmtInfraNumuplinkports and MgmtTenantNumuplinkports for the management cluster

EdgeInfraNumuplinkports and EdgeTenantNumuplinkports for the edge cluster

ResInfraNumuplinkports and ResTenantNumuplinkports for the resource cluster

o If the MgmtHostInfraNic and MgmtHostTenant Nic values for each host are set to a specific NIC, the script assigns the vmnic to the switch after making sure it is available.

NOTE:

1) User can specify a 1G port if needed.

2) The above listed parameters are ignored in this scenario and only the vmnics specified are assigned

3) User can specify a mix of values. Ie. Set MgmtInfraNumuplinkports and MgmtTenantNumuplinkports to blank and assign vmnic values to the Edge and Resource cluster Infra and Tenant VDS. In this case, the given vmnic


18


values are assigned to the Edge and Resource VDS and the first available 10G port if assigned to the Management VDS.

▪ Enable DRS and HA

▪ Setup VCHA

▪ Add hosts to VSAN

Prerequisites:

1) IP addresses and hostnames for all the nodes should be recorded in the DNS server and should be resolvable.

2) Management vCenter Server should be deployed.

Table 6: Input values for Management vCenter configuration


Parameter Name Description Default value

Example

MgmtDCName Management vCenter datacenter name

MgmtDCName=Mgmt-DC

MgmtClusterName Management vCenter cluster name

MgmtClusterName=MGMT-Cluster

InfraDvSwitch Name of the Infra DvSwitch that will be created

InfraDvSwitch=vDS-Mgmt-Infra

TenantDvSwitch

Name of the Tenant DvSwitch that will be created

TenantDvSwitch=


19



Example

NumUplinkPorts

Number of uplink ports. Should be equal to the number of NICs available for each virtual distributed switch

NumUplinkPorts=2

MgmtPGvMotion

Name of the vMotion port group that will be created

MgmtPGvMotion=vDS-PG-vMotion-VLAN11

MgmtPGvMotionVLANID VLAN ID for the vMotion port group

MgmtPGvMotionVLANID=11

MgmtPGESXi Name of the ESXi port group that will be created

MgmtPGESXi = vDS-PG-ESXiMGMT-VLAN10

MgmtPGESXiVLANID VLAN ID of the ESXi port group

MgmtPGESXiVLANID = 10

MgmtPGInfraBackup

Name of the backup port group that will be created on the InfraVDS. If left blank, port group will not be created

MgmtPGInfraBackup = vDS-PG-Backup-VLAN12

MgmtPGInfraBackupVLANID

VLAN ID of the backup port group

MgmtPGInfraBackupVLANID = 12


20



Example

MgmtPGReplication

Name of the replication port group that will be created

MgmtPGReplication = vDS-PG-Replication-VLAN13

MgmtPGReplicationVLANDID

VLAN ID of the replication port group

MgmtPGReplicationVLANID = 13

MgmtPGvSAN Name of the vSAN port group that will be created

MgmtPGvSAN = vDS-PG-Replication-VLAN14

MgmtPGvSANVLANID VLAN ID of the vSAN port group

MgmtPGvSANVLANID = 14

MgmtPGVMMgmt

Name of the VM Mgmt port group that will be created

MgmtPGVMMgmt = vDS-PG-VMMGMT-VLAN15

MgmtPGVMMgmtVLANID VLAN ID of the VM Mgmt port group

MgmtPGVMMgmtVLANID = 15

MgmtPGVCHA

Name of the VCHA port group that will be created

MgmtPGVCHA = vDS-PG-VCHA-VLAN16

MgmtPGVCHAVLANID VLAN ID of the VCHA port group

MgmtPGVCHAVLANID = 16


21



Example

MgmtPGTenantBackup

Name of the backup port group that will be created on the Tenant VDS

MgmtPGTenantBackup = vDS-PG-Tenant-VLAN17

MgmtPGTenantBackupVLANID

VLAN ID of the backup port group

MgmtPGTenantBackupVLANID = 17

MgmtPGExternal

Name of the External port group that will be created

MgmtPGExternal = vDS-PG-External-VLAN18

MgmtPGExternalVLANID VLAN ID of the External port group

MgmtPGExternalVLANID = 18

MgmtHostvMotionIp1

(Add MgmtHostvMotionIp2, MgmtHostvMotionIp3 etc. for the rest of the hosts)

vMotion IP address of the 1st management host

MgmtHostVmotionIp1= x.x.x.x

VMHostvMotionMask Subnet mask for vMotion

VMHostvMotionMask = x.x.x.x

MgmtHostVSANIp1

(add MgmtHostVSANIp2, MgmtHostVSANIp3 etc. for the rest of the hosts)

vSAN IP address for the 1st management host

MgmtHostVSANIp1= x.x.x.x


22



Example

VMHostVSANMask Subnet mask for vSAN

VMHostvSANMask = x.x.x.x

MgmtHostTenantNic1

(add MgmtHostTenantNic2, MgmtHostTenantNic3 etc. for the rest of the hosts)

Vmnic name to assign to the tenant VDS. If multiple nics are to be assigned, enter comma separated values

MgmtHostTenantNic1=vmnic0, vmnic1

MgmtHostInfraNic1

add MgmtHostInfraNic2, MgmtHostInfraNic3 etc. for the rest of the hosts)

Vmnic name to assign to the Infra VDS. If multiple nics are to be assigned, enter comma separated values

MgmtHostInfraNic1=vmnic3

VCHA IP

MgmtVCHAIp

VCHA IP address of the second nic of the management host

MgmtVCHAIp = x.x.x.x

MgmtVCHAPrefix Network prefix MgmtVCHAPrefix = 26

MgmtVCHAPassiveIp VCHA IP address of the passive VCHA appliance

MgmtVCHAPassiveIp = x.x.x.x


23



Example

MgmtVCHAPassiveVmName

Appliance name of the VCHA passive VM

MgmtVCHAPassiveVmName = MGMT-PASSIVE

MgmtVCHAWitnessIp VCHA IP address of the witness VCHA appliance

MgmtVCHAWitnessIp = x.x.x.x

MgmtVCHAWitnessVmName

Appliance name of the witness VCHA appliance

MgmtVCHAWitnessVmName = MGMT-Witness

MgmtVCHASubnetMask Subnet mask for the VCHA network

MgmtVCHAsubnetMask = x.x.x.x

MgmtPGNFS External NFS mgmt. port group name

MgmtPGNFS=NFS-3104

MgmtHostNFSIp1

(add MgmtHostNFSIp2, MgmtHostNFSIp3 etc. for the rest of the hosts)

Mgmt host1 ip address for NFS

MgmtHostNFSIp1=x.x.x.x

8.3 Resource vCenter Deployment and Configuration

Resource vCenter server deployment and configuration

8.3.1 Resource vCenter Deployment

Script Name: Deploy_Resource_vCenterServer.ps1

Deploys resource vCenter server.

Prerequisites:



24


2) Management vCenter Server should be deployed and configured.

Table 7: Input values for Resource vCenter deployment



Example

ResourceVCDeploymentOption

Resource vCenter deployment size

small ResourceVCDeploymentOption=small

ResourceVCApplianceName

Resource vCenter appliance name

ResourceVCApplianceName=RESVC

ResourceVCHostname Resource vCenter FQDN

ResourceVCHostname=resvc.nfvra.com

ResVCName Resource vCenter vm name

ResVCName-resvc

ResourceVCGateway Gateway address to deploy resource vCenter

ResourceVCGateway=x.x.x.x

ResourceVCIpAddress Resource vCenter appliance IP address

ResourceVCIpAddress=x.x.x.x

ResourceVCIpFamily Resource vCenter IP family

IPv4 ResourceVCIpFammily=IPv4


25



Example

ResourceVCNetworkMode Resource vCenter network mode

Static (NOTE:only ‘static’ accepted for this release)

ResourceVCNetworkMode=static

ResourceVCNetworkPrefix Network prefix ResourceVCNetworkPrefix=24

ResourceVCRootPassword

Resource vCenter root password

ResourceVCRootPassword=mypassword

ResourceVCSSOPassword

Resource vCenter SSO password

ResourceVCSSOPassword=myssopassword

ResourceVCSSODomain Resource vCenter SSO domain

ResourceVCSSODomain=vsphere.local

ResourceVCUserName Resource vCenter username

ResourceVCUserName=root

8.3.2 Resource vCenter Configuration

Script Name: Configure_Resource_vCenterServer.ps1

Configures resource vCenter server:

▪ Create a datacenter, cluster and add hosts

▪ Create infrastructure and tenant virtual distributed switch and add port groups

▪ Enable DRS and HA

▪ Setup VCHA

▪ Add hosts to VSAN

Prerequisites:


26



2) Resource vCenter Server should be deployed.

Table 8: Input values for Resource vCenter configuration



Example

ResDCName Resource vCenter Datacenter Name

ResDCName = RES-DC

ResClusterName Resource Cluster Name

ResClusterName = RES-CL

ResInfraDvSwitch Name of the Infra DvSwitch that will be created

ResInfraDvSwitch = RES-INFRA

ResTenantDvSwitch Name of the Tenant DvSwitch that will be created

ResTenantDvSwitch = RES-Tenant

ResNumUplinkports

Number of Uplink ports, should be equal to the number of NICs available for each virtual Distributed Switch

ResNumuplinkports = 2

ResPGvMotion Name of the vMotion port group that will be created

ResPGvMotion = vDS-PG-vMotion-VLAN11

ResPGvMotionVLANID VLANID for the vMotion port group

ResPGvMotionVLANID = 11

ResPGESXi Name of the ESXi MGMT port group that will be created

ResPGESXi = vDS-PG-ESXiMGMT-VLAN12


27



Example

ResPGESXiVLANID VLANID for the ESXi MGMT port group

ResPGESXiVLANID = 12

ResPGvSAN Name of the vSAN port group that will be created

ResPGvSAN = vDS-PG-vSAN-VLAN13

ResPGvSANVLANID VLANID for vSAN port group

ResPGvSANVLANID = 13

ResPGVMMgmt

Name of the VM Management port group that will be created

ResPGVMMgmt = vDS-PG-VMMGMT-VLAN14

ResPGVMMgmtVLANID VLANID for VM Management port group

ResPGVMMgmtVLANID = 14

ResHostvMotionIp1 vMotion Ip address of 1st Resource host

ResHostvMotionIp1 = x.x.x.x

ResVMHostvMotionMask SubnetMask for Resource vMotion

ResHostvMotionMask = x.x.x.x

ResHostVSANIp1 vSAN Ip address of 1st Resource host

ResHostVSANIp1= x.x.x.x

ResVMHostvSANMask SubnetMask for Resource vSAN

ResHostvSANMask = x.x.x.x

ResHostvMotionIp2 vMotion Ip address of 2nd Resource host

ResHostVmotionIp2= x.x.x.x


28



Example

ResHostvSANIp2 vSAN Ip address of 2nd Resource host


ResHostvMotionIp3 vMotion Ip address of 3rd Resource host

ResHostVmotionIp3= x.x.x.x

ResHostvSANIp3 vSAN Ip address of 3rd Resource host


ResVCHAIp

VCHA Ip address of the second NIC of Resource vCenter

ResVCHAIp = x.x.x.x

ResVCHAPrefix Network Prefix ResVCHAPrefix = 26

ResVCHAPassiveIp

VCHA Ip address of the VCHA Passive vCenter appliance

ResVCHAPassiveIp = x.x.x.x

ResVCHAPassiveVmName

Appliance name of the VCHA Passive vCenter

ResVCHAPassiveVmName = RESOURCE-PASSIVE

ResVCHAWitnessIp

VCHA Ip address of the VCHA Witness vCenter appliance

ResVCHAWitnessIp = x.x.x.x

ResVCHAWitnessVmName

Appliance name of the VCHA Witness vCenter

ResVCHAWitnessVmName = RESOURCE-WITNESS

ResVCHASubnetMask Subnet Mask for VCHA Network

ResVCHAsubnetMask = x.x.x.x


29



Example

ResPGOverlay

Name of the Overlay port group that will be created

(this gets created in the Edge VDS for a 3-POD topology and in the Resource VDS for a 2-POD topology)

ResPGOverlay = vDS-RES-OVERLAY

ResPGExternal

Name of the External port group that will be created (this gets created in the Edge VDS for a 3-POD topology and in the Resource VDS for a 2-POD topology)

ResPGExternal = vDS-RES-External

ResHostTenantNic1

(add ResHostTenantNic2, ResHostTenantNic3 etc. for the rest of the hosts)


ResHostTenantNic1=vmnic0, vmnic1

ResHostInfraNic1

add ResHostInfraNic2, ResHostInfraNic3 etc. for the rest of the hosts)


ResHostInfraNic1=vmnic3

ResPGNFS External NFS resource port group name

ResPGNFS=NFS-3104


30



Example

ResHostNFSIp1

(add ResHostNFSIp2, ResHostNFSIp3 etc. for the rest of the hosts)

Resource host1 ip address for NFS

ResHostNFSIp1=x.x.x.x

8.4 Edge Cluster Configuration

Script Name: Edge_Cluster_Configuration.ps1

Configures the Edge cluster (for 3-POD topology only).

Prerequisites:



Table 9: Input values for Edge Cluster deployment



Example

EdgeClusterName Edge Cluster Name EdgeClusterName = EDGE-CL

EdgeInfraDvSwitch Name of the Infra DvSwitch that will be created

EdgeInfraDvSwitch = EDGE-INFRA

EdgeTenantDvSwitch Name of the Tenant DvSwitch in the Edge cluster

EdgeTenantDvSwitch = EDGE-Tenant


31



Example

EdgeNumUplinkports

Number of uplink ports, should be equal to the number of NICs available for each virtual Distributed Switch

EdgeNumuplinkports = 2

EdgePGvMotion Name of the vMotion port group that will be created

EdgePGvMotion = vDS-PG-VMotion-VLAN11

EdgePGvMotionVLANID VLANID for the vMotion port group

EdgePGvMotionVLANID = 11

EdgePGESXi Name of the ESXi MGMT port group that will be created

EdgePGESXi = vDS-PG-ESXiMGMT-VLAN12

EdgePGESXiVLANID

VLANID for the ESXi management port group in the Edge cluster

EdgePGESXiVLANID = 12

EdgePGvSAN

Name of the vSAN port group that will be created in the Edge cluster

EdgePGvSAN = vDS-PG-vSAN-VLAN13

EdgePGvSANVLANID VLANID for vSAN port group

EdgePGvSANVLANID = 13

EdgePGVMMgmt

Name of the VM management port group that will be created

EdgePGVMMgmt = vDS-PG-VMMGMT-VLAN14

EdgePGVMMgmtVLANID

VLANID for VM Management port group

EdgePGVMMgmtVLANID = 14


32



Example

EdgeVMHostvMotionMask

Subnet Mask for Edge vMotion

EdgeVMHostvMotionMask = 255.255.255.0

EdgeVMHostvSANMask Subnet Mask for Edge vSAN

EdgeVMHostvSANMask = 255.255.255.0

EdgeHostvMotionIp1 vMotion Ip address of 1st Edge host

EdgeHostVmotionIp1= x.x.x.x

EdgeHostvSANIp1 vSAN Ip address of 1st Edge host

EdgeHostVSANIp1=x.x.x.x

EdgeHostvMotionIp2 vMotion Ip address of 2nd Edge host


EdgeHostvSANIp2 vSAN Ip address of 2nd Edge host

EdgeHostVSANIp2= x.x.x.x

EdgeHostvMotionIp3 vMotion Ip address of 3rd Edge host


EdgeHostvSANIp3 vSAN Ip address of 3rd Edge host

EdgeHostVSANIp3= x.x.x.x

EdgeHostTenantNic1

(add edgeHostTenantNic2, EdgeHostTenantNic3 etc. for the rest of the hosts)


EdgeHostTenantNic1=vmnic0, vmnic1

EdgeHostInfraNic1

(add EdgeHostInfraNic2, EdgeHostInfraNic3 etc. for the rest of the hosts)


EdgeHostInfraNic1=vmnic3


33



Example

EdgePGNFS External Edge NFS port group name

EdgePGNFS=NFS-3104

EdgeHostNFSIp1

(add EdgeHostNFSIp2, EdgeHostNFSIp3 etc. for the rest of the hosts)

Edge host1 ip address for NFS

EdgeHostNFSIp1=x.x.x.x

8.5 NSX-T Manager Deployment and Configuration

This section covers NSX-T manager deployment and configuration prerequisites and parameters details

8.5.1 NSX-T Manager Deployment

Script Name: Deploy_NSXT_Manager.ps1

Deploys the primary NSX-T appliance. In NSX-T 2.4 version, the NSX-T manager appliance takes on the role of nsx-manager and nsx-controllers. A cluster of 3 NSX managers is deployed for High Availability. The 2 secondary NSX-T managers are deployed in the Config_NSXTManager.ps1 script

Prerequisites:

1) IP addresses and hostnames for the NSX-T primary and secondary nodes should be recorded in the DNS server and should be resolvable.


Table 10: Input values for NSX-T Manager deployment



Example

NsxTMGROVAPath Path to NSX Manager OVA file

NsxTMGROVAPath=E:\\Builds RA 3.0\\nsx-unified-appliance-2.2.0.0.0.8680778.ova


34



Example

NsxTMGRVMName NSX-T Manager VM name

NsxTMGRVMName=NSX-T30

NsxTRootPassword NSX-T Manager root password

NsxTRootPassword=mypwd

NsxTCliPassword NSX-T Manager cli password

NsxTCliPassword=myclipwd

NsxTAdminPassword NSX-T Manager admin password

NsxTAdminPassword=myadminpwd

NsxTAuditPassword NSX-T Manager audit password

NsxTAuditPassword=mypwd

NsxTAdminUserName NSX-T Manager admin userName

NsxTAdminUserName=admin

NsxTAuditUserName NSX-T Manager audit userName

NsxTAuditUserName=audit

NsxTMGRHostName NSX-T Manager HostName FQDN

NsxTMGRHostName= nsxtmgr.nfvra.com

NsxTMGRRole NSX-T Manager role

NsxTMGRRole=nsx-manager nsx-controller

NsxTMGRIpAddress NSX-T Manager IP address

NsxTMGRIPAdress=x.x.x.x

NsxTNetMask NSX-T Manager netmask

NsxTNetMask=x.x.x.x


35



Example

NsxTGateWay NSX-T Manager gateway address

NsxTGateWay=x.x.x.x

NsxTPrefix NSX-T Manager network prefix

NsxTPrefix = 25

NsxTMGRDepSize

NSX-T Manager deployment size. Options are small, medium, large

small NsxTMGRDepSize=small

NsxTIpType

NSX-T Manager IP Type. Options are “IPv4 or IPv6

IPv4 NsxTIPType=IPv4

NsxTMGRFormFactor NSX-T appliance deployment size

SMALL

8.5.2 NSX-T Manager Configuration

Script Name: Config_NSXTManager.ps1

Configures NSX-T manager and deploys the two secondary manager appliances. The following tasks are also completed

▪ Configure license

▪ Add management and resource vCenter servers as compute managers.

▪ Create an NSX-T cluster of the 3 manager nodes

▪ Add hosts

Prerequisites:


36


1) IP addresses and hostnames for the NSX-T manager should be recorded in the DNS server and should be resolvable.


3) Resource vCenter server should be deployed and configured.

4) NSX-T manager should be deployed

Table 11: Input values for NSX-T Controllers deployment



Example

NsxTCtrlNode01IpAddress

NSX-T secondary node ip address

NsxTCtrlNode02IpAddress

NSX-T secondary node ip address

NsxTLoadBalancerSize

NSX-T load balancer size

SMALL

(equates to 20 VSs, 60 pools and 300 pool members)

NsxTLicense

NSX-T Manager license

NsxTLicense=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

8.5.3 NSX-T Manager components for VCD configuration

Script Name: Config_NSXT_For_vCloudDirector.ps1

Deploys NSX-T components needed for vCloud Director configuration.


37


▪ Create two Edge nodes

▪ Create overlay Transport Zone

▪ Create VLAN Transport Zone

▪ Create host switch profile

▪ Create NSX-T IP pool

▪ Create Edge cluster

▪ Create Tier-1 logical router

▪ Create VLAN backed logical switch

▪ Create logical switch and logical router ports

▪ Create TCP health monitor

▪ Create Load Balancer pools

▪ Create virtual server

Prerequisites:

1) NSX-T primary node appliance should be successfully deployed.

2) IP addresses for load balancer VIP should be recorded in the DNS server and should be resolvable.

Table 13: Input values for vRealize Log Insight master and worker nodes deployment



Example

NsxTEdgeNodeIp1 NSX-T Edge node1 ip address

NsxTEdgeNodeIp2 NSX-T Edge node2 ip address


38


Overlay_Transport_Zone_display_name

NSX-T overlay transport zone display name

Overlay_Transport_Zone_host_switch_name

NSX-T overlay transport zone host switch name

Overlay_Transport_Zone_description

NSX-T overlay transport zone description

Overlay_Transport_type Overlay transport type

VLAN_Transport_Zone_display_name

VLAN transport zone display name

VLAN_Transport_Zone_host_switch_name

VLAN transport zone host switch name

VLAN_Transport_Zone_description

VLAN transport zone description

VLAN_Transport_type VLAN transport type


39


NsxTIPPoolStartAddress NSX-T ip pool start address

NsxTIPPoolEndAddress NSX-T Ip pool end address

NsxTIPPoolCIDR NSX-T ip pool CIDR

x.x.x.x/24

8.6 vRealize Log Insight Deployment and Configuration

This section covers vRealize Log Insight deployment and configuration prerequisites and parameters details

8.6.1 vRealize Log Insight Deployment

Script Name: Deploy_vRealizeLogInsight.ps1

Deploys vRealize Log Insight master and two worker nodes.

Prerequisites:

1) IP addresses and hostnames for master, worker nodes and VIP (for integrated load balancer) should be recorded in the DNS server and should be resolvable.


Table 14: Input values for vRealize Log Insight master and worker nodes deployment



40



Example

LogInsightNodeOVAPath

Log Insight OVA file path

LogInsightNodeOVAPath=E:\\Builds RA 3.0\\VMware-vRealize-Log-Insight-4.6.0-8080673.ova

LogInsightMNodeIpAddress

vRealize Log Insight Master Node IP Address

LogInsightMNodeIPAdress=x.x.x.x

LogInsightMNodeVMName

vRealize Log Insight Master Node VM Name

LogInsightMNodeVMName=MGMTLI01

LogInsightMNodeDomainName

vRealize Log Insight Master Node domain name that it is part of

LogInsightMNodeDomainName=mgmtli01.nfvra.com

LogInsightNodeNetMask

vRealize Log Insight subNet mask

LogInsightNodeNetMask=x.x.x.x

LogInsightNodeGateway

vRealize Log Insight Node gateway address

LogInsightNodeGateWay=x.x.x.x

LogInsightNodeDeploymentOption

vRealize Log Insight Node deployment options (small,medium,large,x-large

LogInsightNodeDeploymentOption=small

LogInsightNodeIpType vRealize Log Insight Node IP allocation type

LogInsightNodeIPType=IPv4


41



Example

LogInsightNodeRootPassword

Realize Log Insight Node root password

LogInsightNodeRootPassword=xxxxxxx

LogInsightWNode1IpAddress

vRealize Log Insight Worker Node IP Address

LogInsightWNode1IPAdress=x.x.x.x

LogInsightWNode1DomainName

vRealize Log Insight Worker Node FQDN

LogInsightWNode1DomainName=mgmtli03.nfvra.com

LogInsightWNode1VMName

vRealize Log Insight Worker Node VM Name

LogInsightWNode1VMName=MGMTLI03

LogInsightWNode2IpAddress

vRealize Log Insight Worker Node IP Addres

LogInsightWNode2IPAdress=x.x.x.x

LogInsightWNode2DomainName

vRealize Log Insight Worker Node FQDN

LogInsightWNode2DomainName=mgmtli03.nfvra.com

LogInsightWNode2VMName

vRealize Log Insight Worker Node VM Name

LogInsightWNode2VMName=MGMTLI03

8.6.2 vRealize Log Insight Configuration

Script Name: Config_vRealize_LogInsight.ps1

Configures vRealize Log Insight master and worker nodes

▪ Configure license and NTP server

▪ Join worker nodes to master to form a cluster


42


▪ Enable Integrated Load Balancer

▪ Configure management and resource vCenter adapter in vRealize Log Insight (ESXi hosts are not configured because of lack of API)

▪ Configure vRealize Operations Manager adapter in vRealize Log Insight

▪ Installs all content packs that are downloaded into the

Prerequisites:

1) IP addresses and hostnames for vRealize Log Insight should be recorded in the DNS server and should be resolvable.


Table 15: Input values for vRealize Log Insight configuration



Example

LogInsightLicense vRealize Log Insight License

LogInsightLicense=xxxxx-xxxxx-xxxxx-xxxxx-xxxxx

LogInsightUserName vRealize Log Insight username

LogInsightUserName=admin

LogInsightemailid vRealize Log Insight admin email id

[email protected]

LogInsightVIPAddress vRealize Log Insight VIP address

LogInsightVIPAddress=192.168.45.232

LogInsightVIPFQDN vRealize Log Insight VIP FQDN

LogInsightVIPFQDN=RAID-VRLI-VIP.nfvra.com

8.7 vRealize Operations Manager Deployment and Configuration

This section covers vRealize Operations Manager deployment and configuration

prerequisites and parameters details


43


8.7.1 vRealize Operations Manager Deployment

Script Name: Deploy_vRealizeOperationManager.ps1

Deploys master, replica and data nodes.

Prerequisites:


2) Management and resource vCenter Servers should be deployed and configured.

Table 16: Input values for vRealize Operations Manager master and replica nodes deployment



Example

vRopsOVAPath vROPs OVA path for deployment

vRopsOVAPath=e:\\builds\\vRealize-Operations-Manager-Appliance-7.0.0.10098133_OVF10.ova

vRopsMasterDeploymentSize

Deployment size of the vRealize Operations Manager master node. Options are small, extrasmall, medium and large

small vRopsMasterDeploymentSize=small

vRopsNodeIpType IP type of the vRops nodes.

IPv4 vRopsNodeIpType=IPv4


44



Example

Options are IPv4 or IPv6

vRopsNodeTime

Timezone to be set for the vROPs master node

vRopsNodeTime=Etc/UTC

vRopsNodeAdminPassword

vROPs admin password

vRopsNodeAdminPassword=mypassword

vRopsNodeUserName vROPs admin username

vRopsNodeUserName=admin

vRopsMasterNodeIp vROPs master node ip address

VRopsMasterNodeIp=x.x.x.x

vRopsMasterNodeVMName

Name of the vROPs master node

vRopsMasterNodeVMName=RAID-VROPS-MASTER

vRopsNodeGateway

Gateway address of the vROPs master node

vRopsNodeGateway=x.x.x.x

vRopsNodeNetmask Subnet mask of the vROPs master node

VRopsNodeNetmask=x.x.x.x

vRopsReplicaNodeIp vROPs replica node IP address

vRopsReplicaNodeIp=x.x.x.x

vRopsDataNodeIp1

vRopsDataNodeIp2

vRopsDataNodeIp3

vROPs data node IP addresses

VRopsDataNodeIp=x.x.x.x


45


8.7.2 vRealize Operations Manager Configuration

Script Name: Config_vRealize_Operations_Manager.ps1

Configures vRealize Operations Manager master, replica and data nodes

▪ Configure license

▪ Join master, replica and data nodes to form a cluster and HA enabled

▪ Configure vSphere and vRealize Log Insight solutions

NOTE:

Due to a lack of API support, user will have to navigate through the EULA page manually and complete it before the license appears in the product. Leave the license as evaluation license in the wizard. The actual license is already configured will appear after the wizard completes.

Table 17: Input values for vRealize Operations Manager configuration


Default value

Example

vRopsNodeUserName

vROPs master ode user name

Y

vRopsNodeUserName=admin

vRopsLicenseKey Y vRopsLicenseKey=xxxx-xxxx-xxxx-xxxx

8.8 VMware vCloud Director Deployment and Configuration

This section covers VMware vCloud Director deployment and configuration prerequisites and parameter details

8.8.1 VMware vCloud Director Deployment

Script Name: Deploy_Primary_vCloud_Director.ps1 & Deploy_Standby_vCloud_Director.ps1

Deploys one primary cell and two standby cells as part of the vCloud Director server group. The VCD 9.7 appliance comes with an embedded postgreSQL database.

Prerequisites:


46


1) NFS server should be available with a folder setup to be used as the VCD server group’s transfer space. The contents of this transfer space should be empty during greenfield deployment. If not, VCD deployment fails.

2) VCD license should be available

3) The VCD cell and database IPs and FQDN should be resolvable.

4) Management vCenter server should be deployed and configured.

The following table lists parameters that should be updated in the Input file for deploying VMware vCloud Director 9.7 which is part of NFV 3.2 BOM

Table 18: Input values for VMware vCloud Director


Example

VCDCellPrimaryeth0Ip

Primary cell eth0 ip address for the vCloud Director service

VCDCellPrimaryeth1Ip

Primary cell eth1 ip address for the embedded PostgreSQL DB health

VCDCellPrimaryFqdn vCloud Director primary cell fully qualified domain name

VCDCellStandby1eth0Ip

Standby cell 1 eth0 ip address for the vCloud Director service


Standby cell 1 eth1 ip address for the embedded PostgreSQL DB health


Standby cell 1 eth0 ip address for the vCloud Director service


47



Example


Standby cell 2 eth1 ip address for the embedded PostgreSQL DB health

VCDCellStandbySysName

VCD standby cell system name

VCDCellStandbySysName=vcd-cell-standby

VCDVMName vCloud Director VM name

vCDOVAPath

vCloud Director OVA path

VCDVIP

vCloud Director virtual IP address

VCDVIPPrefix VCloud Director virtual IP prefix

24

VCDNetMask

vCloud Director subnet mask

VCDGateway

vCloud Director gateway address

VCDGuestUser

vCloud Director user name

vCDTRootPassword vCloud Director root password

VCDNFSServerIp vCloud DirectorNFS server IP

VCDNFSServerIp=x.x.x.x


48



Example

VCDNFSShare vCloud Director NFS share name

VCDNFSShare=host:/RAID-Automation/VCD-NFS

VCDIpAllocationPolicy

vCloud Director IP allocation policy. Options are ‘fixedPolicy’ or ‘dhcp’.

fixedPolicy

VCDIpProtocol vCloud Director IP protocol type

IPv4 VCDIpProtocol=IPv4

VCDDBIp vCloud Director database IP

VCDDBIp=x.x.x.x

VCDDBName vCloud Director database name

VCDDBName=vcloud

VCDDBUser vCloud director database user

VCDDBUser=dbuser

VCDDBPassword vCloud director database password

VCDDBPassword=mypassword

VCDDBType vCloud Director database type. Options are mssql or postgres

VCDDBType=mssql

VCDAdminUserName vCloud director admin username

VCDAdminUserName=administrator

VCDAdminFullname vCloud Director admin full name

VCDAdminFullname=VCD Admin

VCDAdminPassword vCloud director admin password

VCDAdminPassword=welcome4

VCDAdminEmail vCloud Director admin email ID

[email protected]


49



Example

VCDSysName vCloud Director system name

VCDSysName=vcd1

VCDInstallID vCloud Director Instance ID

VCdInstallID=1

8.8.2 VMware vCloud Director Configuration

Script Name: Config_vCloud_Director.ps1

Configures the vCloud Director appliance. The following tasks are completed -

▪ Register vCenter server with VCD

▪ Register NSX-T with VCD

▪ Create an Org

▪ Create a Provider VDC

8.9 NSX-V Manager Deployment and Configuration

NSX-V manager deployment and configuration

8.9.1 NSX-V Manager Deployment

Script Name: Deploy_NSXV_Manager.ps1

Deploys NSX-V manager.

Prerequisites:

1) IP address and hostname for NSX-V should be recorded in the DNS server and should be resolvable.

2) Management vCenter Server should be deployed and configured

Table 19: Input values for NSX-V deployment



50



Example

NsxVMGROVAPath NSX manager OVA path

NsxVMGROVAPath=f:\\builds\\VMware-NSX-Manager-6.4.3-9927516.ova

NsxVMGRVMName NSX manager VM name

NsxVMGRVMName=NSXVMGR

NsxVAdminUserName NSX manager admin username

NsxVAdminUserName =admin

NsxVRootPassword NSX manager root password

NsxVRootPassword=xxxxxxxx

NsxVAdminPassword NSX manager admin password

NsxVAdminPassword=yyyyyyy

NsxVMGRHostName NSX manager hostname

NsxVMGRIpAddress NSX manager IP address

NsxVMGRIpAddress=x.x.x.x

NsxVNetMask NSX manager subnet mask

NsxVNetMask=x.x.x.x

NsxVGateway NSX manager gateway address

NsxVGateWay=x.x.x.x

NsxVLicense NSX manager license key

NsxVLicense=


51



Example

NsxVNetwork NSX manager VM network

NSXvNetwork = INFRAMGMT1825

8.9.2 NSX-V Manager Configuration

Script Name: Config_Resource_NSXV.ps1

Configures NSX-V manager.

▪ Register resource vCenter server with NSX-V manager

▪ Deploy 3 controller nodes

▪ Apply NSX license

▪ Resource cluster host preparation

▪ Edge cluster host preparation (if 3-POD topology)

▪ Create VTEP IP pool, configure VXLAN

▪ Add segment ID and transport zone

Prerequisites:

1) IP address and hostname for NSX-V should be recorded in the DNS server and should be resolvable.

2) Management vCenter Server should be deployed and configured

Table 20: Input values for NSX-V configuration



Example

ControllerIpPoolName NSX-V Controller IP Pool Name

ControllerIpPoolName=TestIpPool

NsxVPrefix Network Prefix NsxVPrefix=25


52



Example

NsxVIpPoolStartAddress

NSX-V Controller IP Pool Start Address

NsxVIpPoolStartAddress=x.x.x.x

NsxVIpPoolEndAddress

NSX-V Controller IP Pool End Address

NsxVIpPoolEndAddress=x.x.x.x

NsxVControllerPassword NSX-V Controller Password

NsxVControllerPassword=xxxxxxxxxx

NSX_VXLAN_Ip_Pool_Name

NSX-V VXLAN IP Pool Name

NSX_VXLAN_Ip_Pool_Name=TestVXLANIpPool

NSX_VXLAN_Ip_Pool_Gateway

NSX-V VXLAN IP Pool Gateway

NSX_VXLAN_Ip_Pool_Gateway=x.x.x.x

NSX_VXLAN_Ip_Pool_Prefix

VXLAN Ip Pool prefix

NSX_VXLAN_Ip_Pool_Prefix=22

NSX_VXLAN_Ip_Pool_Start VXLAN Ip Pool start address

NS_VXLAn_Ip_Pool_Start=x.x.x.x

NSX_VXLAN_Ip_Pool_End VXLAN Ip Pool end address

NSX_VXLAN_Ip_Pool_End=x.x.x.x

NSX_VXLAN_VTEP_Count Number of VXLAN tunnel endpoints

1 NSX_VXLAN_VTEP_Count=1

NSX_VXLAN_VLANID VLAN Id for VXLAN

NSX_VXLAN_VLANID=1825


53



Example

NSX_VXLAN_TZ_Name NSX-V transport name

NSX_VXLAN_TZ_Name=TZ-Resource

NSX_VXLAN_TZ_Mode NSX-V transport Mode

NSX_VXLAN_TZ_Mode=UNICAST_MODE

NSX_VXLAN_Segment_ID_Begin

NSX-V segment ID pool range start

NSX_VXLAN_Segment_ID_Begin=5000

NSX-VXLAN_Segment_ID_End

NSX-V segment ID range end

NSX_VXLAN_Segement_ID_End=5999

NSX_VXLAN_Failover_Mode

Failover mode for NSX_VXLAN

NSX-VXLAN_Failover_Mode=FAILOVER_ORDER

NSX_VXLAN_MTU_Size MTU size for the VXLAN network

NSX_VXLAN_MTU_Size=

1600

9 General purpose scripts

Cleanup_VSAN_Configuration.ps1: This script can be used to clean up the VSAN configuration on all the hosts listed in the input file. It begins by powering off and deleting all the VMs on each host. It then removes the VSAN storage device from the host. And finally, it removes the host from the VSAN cluster.

Config_Pre_Deploy_Storage.ps1: This script prepares the initial storage in the management cluster for management vCenter server deployment.

If the storage to be used for the management cluster is VSAN, the script creates a single node VSAN cluster on the first management host.

If the storage to be used for the management cluster is NFS and if the vmkernel ips for the individual hosts and vlan ID are specified in the input file, the script adds the vmkernel ip to the Infra VDS and mounts the NFS share on the first host. If the vmkernel


54


ips are not specified in the input file, the script proceeds to mount the NFS share on to the host. In this case, it is assumed that the management and NFS share the vmkernel adapter.

10 Functions implementation

Util.ps1: Util.ps1 file is a PowerShell module. It is a utility script containing several functions. These functions are reused in several scripts in RAID. Below are some examples of functions which are in the util.ps1 module -

1. Deploy-vApp: This function is used to deploy any vAPP and configure its network/os parameters. This function is used extensively in RAID to deploy NSX Manager, NSX-T Manager, VCD Cells, vRealize Operation Manager Nodes, vRealize Loginsight Nodes etc. Usage: $DeployStatus = Deploy-vApp -VMName $VMName -ovfconfigParams $OvfConfigParams -ovffile $OVAFilename -vmhost $VMHost -datastore $DataStore Where $VMName = vApp name $OvfConfigParams = OVF configuration parameters $OVAFilename = path to the OVF file $VMHost = host on which to deploy the vApp $DataStore = datastore on which to deploy the vApp

2. ClaimDisk: Disk selection can be set to ‘manual selection’ during VSAN datastore creation. The user can then use this function to select specific disks to be claimed by VSAN during disk group creation. The VSAN type supported is Hybrid Mode. Usage: ClaimDisk $HostIp $VCConfigParam.MgmtHostUser $VCConfigParam.MgmtHostPassword Where $HostIp = host whose disks will be claimed for VSAN $VCConfigParam.MgmtHostUser = host login username $VCConfigParam.MgmtHostPassword =host login password

3. JoinCluster: Single Node vSAN feature is used in the automation. Once the

vSAN datastore is created with the single node, use this function to join datastores from the other ESXi hosts to the single node vSAN cluster. The vSAN sub cluster uuid is used to join the other hosts to the vSAN Cluster.


55


Usage: JoinCluster $HostIp $VCConfigParam.MgmtHostUser $VCConfigParam.MgmtHostPassword $VCConfigParam.MgmtHostIp1 Where $HostIp = host whose disks will be added to the VSAN cluster $VCConfigParam.MgmtHostUser = host login username $VCConfigParam.MgmtHostPassword = host login password $VCConfigParam.MgmtHostIp1 = host ip address where the single node VSAN cluster resides

4. GetFreePnic: This function fetches the list of NICs which are free/unassigned

and 10Gig. Once this information is available, the automation script picks the first one from the list and assigns the uplink to the Infra/Tenant DvSwitch. Usage: $HostVMnic = GetFreePnic $ip $VCConfigParam.MgmtHostUser $VCConfigParam.MgmtHostPassword Where $ip = host ip address $VCConfigParam.MgmtHostUser = user name $VCConfigParam.MgmtHostPassword = password

5. MountNFS: Mounts NFS storage on ESXi hosts.Before mounting the hosts, the script checks to see if parameters are provided in the input file to add a vmkernel adapter. If so, the script adds a vmkernel adapter on each host and then mounts the NFS share on the hosts

Usage: MountNFS $ESXiIP, $ESXiUser, $ESXiPassword, $NFSIp, $NFSMountPoint, $NFSName, $vlanid, $ip, $subnet, $switchname, $MgmtNFSPGName Where $ESXiIP = host on which to mount NFS share $ESXiUser/$ESXiPassword = ESXi host login credentials $NFSIp = IP of the NFS server $NFSMountPoint = mount point for NFS $NFSName = NFS datastore name $vlanid = vlan id on which to create a port group for NFS $ip = NFS vmkernel adapter static ip for host $subnet = subnet $switchname = switch on which to create the NFS portgroup $MgmtNFSPGName = name of the NFS port group


56


6. VMDeletion: Power off and delete all VMs from the given host. Usage: VMDeletion $ESXiIP, $ESXiUser, $ESXiPassword Where $ESXiIP = host from which to delete all VMs $ESXIUser/$ESXiPassword = ESXi host login credentials 7. DrsRule: Sets DRS anti-affinity rules for the various product components. Anti-

affinity rules for the following components are added to the management vCenter:

❖ Management VCHA vms

❖ Resource VCHA vms

❖ vRealize Operations Manager master and data nodes

❖ vRealize Log Insight master and worker nodes

❖ vCloud Director cells

❖ vRealize Network Insight proxy vms

11 Troubleshooting

This section is a compilation of commonly seen issues that were encountered during testing.

1) Issue: Errors related to new-VM creation are displayed in the powercli console during VCHA VM cloning phase (see screenshot below). Cause: These errors are printed when there are intermittent network issues in the testbed and the timeout set for the operation to complete has completed. This is mostly seen when the product is being deployed on NFS storage. Resolution: Let the script continue and complete. Log into the vSphere web client. If the cloning process is proceeding and there are no errors reported, let it finish


57


2) Issue: Script errors out with message: VM already exists. Cause: This script is meant to be used only for greenfield deployment (ie. to deploy products for the first time only). Resolution: If the user needs to reinstall a product, then the user has to make sure the existing version is completely uninstalled before using the deployment script again.

12 Authors list

Arunkumar Kodagi Ramachandra, Solutions Architect, NFV Solutions, VMware

Uma Murthy, Solutions Consultant, NFV Solutions, VMware

Ashish Chanda, Solutions Consultant, NFV Solutions, VMware

Many thanks for contributions and feedback from:

Ganesh Borle, Solutions Consultant, NFV Solutions, VMware

Reference Architecture Infrastructure Deployer (RAID) for NFV · 2019-12-18 · Reference...

Documents

Transcript of Reference Architecture Infrastructure Deployer (RAID) for NFV · 2019-12-18 · Reference...