Review of the vSphere with VDS Install Guide through the AVI config steps

[cdelashmutt-pivotal]

Here is review of the content in the install guide through the AVI configuration.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html
- Consider versioning these guides and refarchs so customers can switch between them to view previous versions (perhaps this is the start of an "edition release"?).
- For all the networking details, I've often seen customers have a need to collect up the entirety of their networking requests and make them into one big request to their networking team. It might be useful to restructure the instructions to have followers of the guide fill out a worksheet with all the details needed, and then just refer back to that worksheet in the instructions.

Near: https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#gen-requirements
- "A datastore with sufficient capacity for the control plane and worker node VM files"
○ Consider adding an actual size here as this is very vague and has no instructions on how someone might go about finding the proper sizing for those files.
- "Depending on the OS flavor of the bootstrap VM, downloadand"
○ Needs a space between "download" and "and".
- "Download and import NSX ALB 20.1.6 OVA to Content Library."
○ Consider providing a link to download.
- "Download the following OVA and import to vCenter. Convert the imported VMs to templates."
○ Consider pluralizing "OVA" to "OVAs" as there are two to download.
- Mulitple links in this section are not directly going to the intended locations, and are instead linking through google.com.

Near: https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#ex-net-entr
- The title of this section as "Network Entries" is a little vague. "Network Entries" to what? If the intent here is to have folks create a table, let's be specific about that. Consider "Planning Networking" or "Networking Worksheet" or something like that, and then rework the top paragraph to support the idea of the work we're expecting followers of the guide to do.

Near: https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#firewall-req
- Consider adding some supporting detail here to note that we're talking about any firewall that governs the networking between the port groups identified in the above table.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=in%20Firewall%20Recommendations.-,Resource%20Pools,-Ensure%20that%20resource
- Consider changing the title of this section to be "Resource Pools and Folders".

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Ensure%20that%20resource%20pools%20and%20folders%20are%20created%20in%20vCenter.
- Consider changing to "Ensure that the following resource pools and folders are created in vCenter".
- Also consider pulling the table in this section into a centralized worksheet that the guide follower fills out.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=availability%20and%20resiliency.-,**Note%3A**Tanzu,-Essential%20licensing%20only
- "**Note:Tanzu Essential licensing on"
○ It seems like the intent here was to "bold" the "Note:" part, but there is no space between the formatting markup ( characters) and the subsequent text (Tanzu).

Near: https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#dep-nsx-alb
- In this section, consider turning the table with "sample IP and FQDN" into an instruction to fill out a worksheet to capture that info.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=imported%20to%20the%20content%20library.
- Should probably reword to say "import into a content library" and mention one could be created for NSX-ALB, or an existing library could be created.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=%E2%80%9Cnsx-alb-components%E2%80%9Dand%20place%20it%20under%20the%20folder%E2%80%9Cnsx-alb-components%E2%80%9D%20.
- Spacing on this line between quote characters and the period seems wrong.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=vCenter%3E%20Home%3E%20ContentLibraries
- Spacing between greater-than symbols and surrounding text, and "ContentLibraries".

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Login%20to%20vCenter%3E%20Home%3E%20ContentLibraries
- This step needs to be broken out into more instructions. Seems like there should be a "Login to vCenter" step, and then a "Navigate to Content Libraries" step that tells someone to click the triple horizontal line menu icon, and select "Content Libraries" from the left side menu.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Select%20name%20and%20Folder
- Capitalization needs to match the capitalization of this screen name in vCenter when referring to the screen name. "Select a name and folder".
- Also consider bolding or quoting this phrase as it refers to a specific screen name.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=select%20a%20Folder%C2%A0for%20the%20NSX%20ALB%20VM%20as%20%E2%80%9Cnsx-alb-components%E2%80%9D
- Folder should not be capitalized.
- The folder name listed here is the "sample" folder name and so should be changed to reference the name of the folder that the guide follower has chosen for their install back in the "Resource Pools" section.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Select%20a%20Compute%20resource
- Capitalization needs to match the capitalization of this screen name in vCenter when referring to the screen name. "Select a compute resource".
- Also consider bolding or quoting this phrase as it refers to a specific screen name.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=select%20the%20resourcepool%C2%A0%E2%80%9Cnsx-alb-components%E2%80%9D
- "resourcepool" should be "resource pool".
- This resource pool name is just the sample one and so should be changed to reference the name of the resource pool that the guide follower has chosen for their install back in the "Resource Pools" section.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=On%20the-,Review%20details,-page%2C%20verify%20the
- Consider bolding or quoting this phrase as it refers to a specific screen name.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=On%20the%20Selectstorage%C2%A0page%2C%20select%20a%20storage%20policy%20from%20the%20VM%20Storage%20Policy%20drop-down%20menu%20and%20choose%20the%20%C2%A0datastore%20location%20where%20you%20want%20to%20store%20the%20virtual%20machine%20files
- "Selectstorage" should be "Select storage". Also consider bolding or quoting this phrase as it refers to a specific screen name.
- Check spacing between "choose the datastore location".
- Where we refer to selecting a storage policy, consider adjusting these instructions to something like "adjust the VM Storage Policy setting if needed to find the datastore you wish to use to store the VM files for the NSX Advanced Load Balancer. Then select the datastore you wish to use by clicking the radio button on the line for that datastore in the table list."

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=select%20the%20network%20%E2%80%9Cnsx_alb_management_pg%E2%80%9D
- The portgroup name here is the sample portgroup name and should refer back to the name the guide follower has chosen for their portgroup for the "NSX ALB Mgmt Network" network.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=On%20the-,Customize%20Template,-page%2C%20provide%20the
- Change case to match UI "Customize template".
- Consider bolding or quoting this phrase as it refers to a specific screen name.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=NSX%20ALB%20Management-,networkdetails,-%2C%20such%20as%20IP
- "network details".

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Note%3A%20If%20you%20choose%20to%20use%20DHCP%2C%20these%20entries%20can%20be%20left%20blank
- Should we promote the use of DHCP for the controllers? This seems like an antipattern as they won't know the MAC addresses for the VMs ahead of time to provide fixed IPs for them.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Note%3A%20While%20the%20system%20is%20booting%20up%2C%20a%20blank%20web%20page%20or%20a%20503%20status%20code%20may%20appear.
- Consider calling out this note more prominently so that guide followers will more likely see this note and not panic when they see it when accessing the controller.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Set%20backup%20Passphraseand%20provide%20DNSinformation%20and%20click%20Next
- This line seems really garbled and doesn't exactly line up with the text in the UI.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Under%20Emal/SMTP%3A%20Provide%20Emailor%20SMTP%C2%A0information
- This line seems really garbled, and probably needs to provide more guidance to the guide follower about their options in the screen.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=IP%20Route%20Domain%3A%20Share%20IP%20route%20domain%20across%20tenants
- Consider indenting, or making this section a table to make the setting names and values easier to read.
- Also it feels like we're missing a step to tell the guide follower to click "Ok" or "Save" or something to commit these initial settings for AVI.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=To%20Configure%20NTP%2C%20navigate%20to%20Administration%3E%20Settings%3E%20DNS/NTP%20%3E%20Edit%20and%20add%20your%20NTP%20server%20details%20and%20Save
- Consider adding something like "After the initial welcome setup steps, click on the triple horizontal lines in the upper left of the screen to access the menu. Navigate to…"
- The spacing between greater-than signs and titles is inconsistent.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=This%20document%20focuses%20on%20enabling%20NSX%20ALB%20using%20the%20license%20model%3A%20Essentials%20License%20(NSX%20ALB%20essentials%20for%20Tanzu)
- No period on this first line.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=By%20default%20evaluation%20license%20will%20be%20making%20use%20of%20Enterprise%20license%2C%20if%20you%20intend%20to%20use%20the%20Enterprise%20Licensing%20features%2C%20you%20may%20add%20your%20license%20key%20in%20the%20licensing%20section%20or%20change%20the%20license%20model%20to%20%E2%80%9CEssentials%E2%80%9D
- Consider reducing the complexity of this line to something like "If you have a different license you want to apply, make sure to select the appropriate license type, and enter any license keys you want to apply for that type in the "Licensing" section.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Refer%20NSX%20Advanced%20Load%20balancer%20Editions%C2%A0for%20comparison%20of%20available%20editions.
- Capitalization of NSX Advanced Load Balancer.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=To%20change%20the%20license%20edition%20to%20Essentials%2C
- Consider "To change the NSX Advanced Load Balancer license model to the Essentials license,".

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Login%20to%20NSX%20ALB%20%3E%20Administration%3E%20Settings%3E%20Licensing%2C%20on%20licensing%20page%20click%20on%20gearicon%C2%A0next%20to%20Licensing
- Inconsistent spacing between greater-than symbols and terms.
- We've already "logged in" so we probably want to change the term to "Via the triple horizontal line menu at the upper left side of the screen, navigate to… Select the Settings menu item from the top screen menu, and then select "Licensing" from the sub-menu".
- Separate the click on gear icon instructions into a separate instruction.
- Also, be specific and tell the guide follower to "click the gear icon next to the "Licensing heading in the resulting page".

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=steps%20to%20configure-,AVI%20ALB%20HA,-%3A
- Should be NSX ALB High Availability.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Set%20the%20Cluster%20IP%20for%20the%20NSX%20ALB%20controllerLog%20in%20to%20the%20primary%20NSX%20ALB%20controller%20%3E%20Navigate%20to%20Administrator%3E%20Controller%3E%20Nodes%2C%20and%20click%20Edit.%20The%20Edit%20Controller%20Configuration%20popup%20appears
- Inconsistent spacing between terms and greater-than symbols.
- Needs to end with a period.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=In%20the%20Controller%20Cluster%20IP%20field%2C%20enter%20the%C2%A0Controller%20Cluster%20IPfor%20the%20Controller%20and%20click%20on%20save
- Check spacing for "IPfor".
- We should call out that this "Controller Cluster IP" is the "HA Address" from the IP/FQDN table earlier in the instructions. And consider changing both terms to be "Controller Cluster IP" so that they are consistent.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Now%20deploy%202nd%20and%203rd%20NSX%20ALB%20Node%2C%20using%20steps%20provided%20here
- The link in this sentence doesn't seem to link to what was intended.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Log%20into%20the%20Primary%20NSX%20ALB%20controller%20using%20the%20Controller%20Cluster%20IP/FQDN%2C%20navigate%20to%20Administrator%3E%20Controller%C2%A0%3E%20%C2%A0Nodes%2C%20and%20click%20Edit.%20The%20Edit%20Controller%20Configuration%20popup%20appears
- Inconsistent spacing between greater-than symbols and terms.
- No period at the end.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Going%20forward%20all-,NSXL%20ALB,-configurations%20will%20be
- Should be "NSX ALB".

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Follow%20the%20below%20steps%20to%20create%20a%20Controller%20certificate
- Consider a colon at the end of this statement as it leads into a list.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=a%20Controller%20certificate-,Login,-to%20NSX%20ALB
- We've already "logged in" so we probably want to change the phrase to something like "Via the triple horizontal line menu at the upper left side of the screen and select "Templates." Select the "Security" menu item from the top screen menu, and then select "SSL/TLS Certificates" option from the sub-menu".

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Click%20on%20Createand%20Select%20Controller%20Certificate
- Spacing issue.
- Consider elaborating more on the location of items to click. "Click on the "Create" button on the right side of the screen above the list of SSL/TLS Certificates. In the resulting drop down menu, select "Controller Certificate."

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Provide%20all%20required%20details%20as%20per%20your%20infrastructure%20requirements%2C%20and%20under%20the%20Subject%20Alternate%20Name%20(SAN)%20section%2C%20provide%20IP%20and%20FQDN%20of%20all%20NSX%20ALB%20controllers%20including%20NSX%20ALB%20cluster%20IP%20and%20FQDN%2C%20and%20click%20on%20Save
- Consider referring back to a worksheet table back in the beginning that captured the FQDNs and IP Addresses for NSX ALB the guide follower

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=and%20then%20click%20on%20%E2%80%9CCopy%20to%20clipboard%E2%80%9D%20under%20the%20certificate%20section
- Consider specifically suggesting the guide follower paste the contents of their clipboard to a file, and give them a suggested name and path so they can reference it later on when needed.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=To%20replace%20the%20certificate%20navigate%20to%20Administration%3E%20Settings%3E%20AccessSettings%2C%20and%20click%20the%20pencil%20icon%20at%20the%20top%20right%20to%20editthe%20System%20Access%20Settings%2C%20replace%20the%20SSL/TSL%20certificate%20and%20click%20on%20Save
- Start off by explaining that although the guide follower has generated a new certificate, they still need to set the Avi Controller Cluster to use that certificate.
- Spacing issues between two words and greater-than symbols and menu terms.
- Direct guide followers to the right spot with a little more elaboration on the instructions. "Via the triple horizontal line menu at the upper left side of the screen and select "Administration." Select the "Settings" menu item from the top screen menu, and then select "Access Settings" option from the sub-menu". Then follow on with the rest of the instructions.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=called%20a%20%E2%80%9Ccloud%E2%80%9D.-,Below%20procedure,-provides%20steps%20on
- "The procedure below"

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=VMware%20vCenter%20cloud-,%2C,-and%20as%20shown
- Change to period and separate into two sentences

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Login%20to%20NSX%20ALB%20%3E%20Infrastructure%20%3E%20Clouds%20%3E%20Create%20%3E%20VMware%20vCenter/vSphere%20ESX
- Separate login from the navigation
- Direct guide followers to the right spot with a little more elaboration on the instructions. "Via the triple horizontal line menu at the upper left side of the screen and select "Infrastructure." Select the "Clouds" menu item from the top screen menu. Next, click on the "Create" button on the right side of the screen above the list of Clouds. In the resulting drop down menu, select "VMware vCenter/vSphere ESX"

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Under%20the%20Infrastructure%20pane%2C%20provide%20vCenter%20Address%2C%20username%2C%20and%20passwordand%20set%20AccessPermission%C2%A0to%20%22Write%22%20and%20click%20on%20Next
- Split into multiple statements and fix spacing.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Under%20the%20Datacenter%C2%A0pane%2C%20Choose%20the%20Datacenter%20for%20NSX%20ALB%20to%20discover%20Infrastructure%20resources
- Too many references to "Datacenter" make this statement confusing. Consider: "Under the Data Center step of the wizard, click the drop down list labeled "Data Center" to select the vSphere Data Center you plan to install your Tanzu Kubernetes Grid Management Cluster and workload clusters to."
- Also, this screen shot looks like it was taken "outside" of the creation wizard. This could lead to confusion as it wouldn't match what a guide follower would actually see.
- Tell the user to click next.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Under%20the%20Networkpane%2C%20choose%20the%20NSX%20ALB%20ManagementNetworkfor%20Service%20Engines%20and%20provide%20a%20StaticIPpoolfor%20SEs%20and%20VIP%20and%20click%20on%20Complete
- Spacing issues
- Consider: "Under the Network step of the wizard, click the drop down list labeled "Management Network" and select the network labelled "NSX ALB Management" in the worksheet at the beginning of this guide."
- Also, this screen shot looks like it was taken "outside" of the creation wizard. This could lead to confusion as it wouldn't match what a guide follower would actually see.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Service%20Engine%20Grouptab
- Spacing

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=To%20create%20a%20Service%20Engine%20group%20for%20TKG%20management%20clusters%2C%20click%20on%20the%20Service%20Engine%20Grouptab%2C%20under%20Select%20Cloud%2C%20choose%20the%20Cloud%20created%20in%20the%20previous%20step%2C%20and%20click%20Create
- Consider: "Next, we need to create a Service Engine group for the TKG Management Cluster. Click on the "Service Engine Group" menu item at the top of the screen. In the drop down list at the top of the page labeled "Select Cloud:", select the name of the Cloud that you created in the previous step. Click the "Create" button on the far right side of the screen.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=only%20management%20Network%20has%20been%20configured%20in%20NSX%20ALB%2C%20follow%20the%20below%20procedure%20to%20configure%20the%20following%20networks
- Consider changing to: "only the NSX ALB Management Network has been configured so far. Follow the procedure below to configure the remaining networks:"

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Login%20to%20NSX%20ALB%20%3E%20Infrastructure%3E%20Networks
- Consider changing to: "Login to the NSX ALB Controller if needed. Then, click on the triple horizontal line menu at the upper left side of the screen and select "Infrastructure." Select the "Networks" menu item from the top screen menu."

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Click%20on%20the%20edit%20icon%20next%20for%20the%20network%20and%20configure%20as%20below.%20Change%20the%20details%20provided%20below%20as%20per%20tour%20SDDC%20configuration
- Consider changing to: "For each of the additional networks to configure from the list in the start of this section, click the edit icon next to the cooresponding port group for each network. Change the settings of each network using the below table as a guide. The subnet and static IP pool will be unique to your particular networking requirements."

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=networks%2C%20for%20example%3A-,%E2%80%9Ctkg_cluster_vip_pg%E2%80%9D,-Once%20the%20networks
- Use the network name here instead of the port group.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Once%20the%20networks%20are%20configured%2C%20set%20the%20default%20routes%20for%20all%20VIP/Data%20networks
- Consider: "Now you need to set the default routes for all VIP Networks.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=add%20default%20routes-,for%20below%20networks,-Change%20the%20gateway
- Consider: "for the port groups cooresponding with the VIP networks identified at the beginning of this guide."

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Change%20the%20gateway%20for%20VIP%20networks%20as%20per%20your%20network%20configurations
- Consider: "The table below is just an example. You port group, gateway and next hop settings will be unique to your installation environment"

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=in%20NSX%20ALB%2C-,expect,-for%20TKG%20Management
- Should be "except"

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=At%20this%20point%20all%20the%20required%20networks%20related%20to%20Tanzu%20functionality%20are%20configured%20in%20NSX%20ALB%2C%20expect%20for%20TKG%20Management%20and%20Workload%20Network%20which%20uses%20DHCP%2C%20NSX%20ALB%20provides%20IPAM%20service%20for%20TKG%20Cluster%20VIP%20Network%2C%20TKG%20Mgmt%20VIP%20Network%20and%20TKG%20Workload%20VIP%20Network
- This sentence needs to be broken out into multiple sentences.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Follow%20below%20procedure%20to%20create%20IPAM%20profile%20and%20once%20created%20attach%20it%20to%20the%20vCenter%20cloud%20created%20earlier
- Consider: "Follow the procedure below to create an IPAM profile and attach it the the vCenter Cloud you created earlier."

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Login%20to%20NSX%20ALB%20%3E%20Infrastructure%3E%20Templates%3E%20IPAM/DNS%20Profiles%3E%20Create%C2%A0%3E%C2%A0IPAM%20Profileand%20provide%20below%20details%20and%20click%20on%20Save
- Consider: "Login to the NSX ALB Controller if needed. Then, click on the triple horizontal line menu at the upper left side of the screen and select "Templates." Select the "Profiles" menu item from the top screen menu. Select the "IPAM/DNS Profiles" sub menu item from the top screen menu.
Next, click on the "Create" button, and select "IPAM Profile" from the drop down list.
Use the settings below to fill out the resulting form."

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Tanzu-vcenter-01%2C%20created%20here
- This should reference whatever cloud name the guide follower chose for their cloud.

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Now%20attach%20the%20IPAM%20profile%20to%20the%20%E2%80%9Ctanzu-vcenter-01%E2%80%9D%20cloud
- Consider: "Now you need to attach the IPAM profile you just created to the Cloud you created earlier."

https://docs-staging.vmware.com/en/VMware-Tanzu/services/tanzu-reference-architecture/GUID-vmware-tanzu-deployment-on-vsphere.html#:~:text=Navigate%20to%20Infrastructure%3E%20Clouds%3E%20Edit%20the%20tanzu-vcenter-01cloud%20%3E%20Under%20IPAM%20Profile%20choose%20the%20profile%20created%20in%20previous%20step%20and%20Save%C2%A0the%20configuration
- Consider: "Click on the triple horizontal line menu at the upper left side of the screen and select "Infrastructure." Select the "Clouds" menu item from the top screen menu. Edit the Cloud you created earlier by clicking the pencil icon on the right side of the screen that cooresponds to the row that contains your Cloud name.
At the bottom of the "Infrastructure" tab in the resulting dialog, click the drop down list labeled "IPAM-Profile" and select the IPAM Profile you just created.
Click the "Save" button at the bottom right corner of the dialog."

[smuthukumar-vmw]

With the new RA, we have worked with IX team and have addressed no formatting errors are observed. Also, from the latest RA, majority of the feedback have been integrated.

https://docs.vmware.com/en/VMware-Tanzu-for-Kubernetes-Operations/2.1/tko-reference-architecture/GUID-reference-designs-tko-on-vsphere.html

https://docs.vmware.com/en/VMware-Tanzu-for-Kubernetes-Operations/2.1/tko-reference-architecture/GUID-deployment-guides-tko-on-vsphere.html