1. Log into the VMCEXPERT VCDR Org assigned to your workshop (VMCEXPERT1-VCDR01, VMCEXPERT2-VCDR01, VMCEXPERT3-VCDR01)
   • username: [email protected]
   • password: {assigned_password}
2. Click View Details
3. Confirm the following:
   1. There are 4 Nodes deployed in the SDDC
   2. Tanzu Service Activated Successfully
      (If the service is not activated you can activate manually or contact us in the Slack Channel).
   3. The SDDC has Large Appliances

4. Click the Networking and Security tab
5. Click Groups --> Management Groups and create the following groups

6. Click Gateway Firewall --> Management Gateway and create the following Firewall rule to allow access to vCenter

7. Click Open vCenter
8. Click Show Credentials
   • Copy the cloudadmin user password
9. Click Open vCenter
10. Login as:
    • Username: [email protected]
    • Password: {Paste in the copied password}
11. Confirm the following
    1. There are 4-nodes in the cluster
    2. There is a Namespaces ResourcePool
    3. There is a kubernetes Content Library

1. In the Summary tab of the SDDC, Click the Actions drop-down
2. Click Activate Tanzu Kubernetes Grid
3. Use the following values to configure the Networks:

4.  Click Validate and Proceed
5.  Click Activate Tanzu Kubernetes Grid

Each lab kit now has an additional Desktop (Tanzu Desktop). Students access this desktop from their VDI session (There is a rdp shortcut to it on their desktop). These desktops are configured on the 10.10.6.0/24 network. There is a vPod router (10.10.6.1) that these desktops use as a gateway. This router also acts as a VPN endpoint to the Desktop. In VMC you setup the VPN to point to this endpoint.

Below is the IP permanent IP address of the vPod Router for Each environment.

1. In the SDDC, click the Networking and Security Tab
2. Click VPN
3. Click Add VPN
4. Enter the following values for the VPN Configuration:
   • NAME:  Tanzu VPN
   • Remote Public IP: {Router IP for your Environment} See the table above
   • BGP Local IP/Prefix Length: 169.254.111.30/30
   • BGP Remote IP: 169.254.111.29
   • BGP Neighbor ASN: 65001
   • Preshared Key: VMwareNinja1!
5. Click Save

1. Go to https://vdi.27virtual.net and login as:
   • Username: vmcexpert#-32
   • Password: {Your_On-Prem_VDI_Password}
2. Select your VDI Desktop
3. Launch google chrome browser
4. Go to https://vmc.vmware.com/console/sddcs, login and select the your Environment VCDR Org
5. Click View Details
6. Click Networking & Security --> VPN
7. Select the Info icon next to Public IP, then copy and save the SDDC VPN Local Gateway IP

8. On the desktop open Notepad and paste in the IP copied in the previous step
9. Launch MTPutty
10. Launch the saved SSH session to the VyOS router

11. Type config to put the router in configuration mode
12. Resize or minimize the MTPutty window
13. On the desktop open the Tanzu VPN Setup Files folder
14. Open and copy the content of the VYOS Tanzu Template for... VPN file
15. Paste the content into another Notepad instance
16. On the Keyboard press CTRL+H
17. Type X.X.X.X in the find field and
18. Paste in the {saved IP from step 7} in the Replace with field
19. Click Replace All

20. Copy all the line that start with set vpn
21. Paste them into the MTPutty  session to the VyOS router
22. Press Enter (This will configure the VPN Endpoint to your SDDC)

23. Return to Notepad and copy the next set of commands under the set vpn commands  (commit through reboot)
24. Press Enter
25. When Prompted Type Y to reboot the Router
26. Close the MTPutty session when prompted

27. In the Browser window with the VMC Console, enable the VPN session
28. Refresh the configuration
29. Your VPN should now report as up ans healthy

1. In the SDDC click the Networking and Security Tab
2. Click Groups
3. Click Add Group
4. Define the following Compute Groups:
   1. Tanzu Egress
      • Group Name: Tanzu Egress
      • Group Type: IP Address
      • Members: 10.240.0.0/22
   2. Tanzu Egress
      • Group Name: Tanzu Ingress
      • Group Type: IP Address
      • Members: 10.240.4.0/22
   3. RFC 1918
      • Group Name: RFC1918
      • Group Type: IP Address
      • Members:
        1. 10.0.0.0/8
        2. 172.16.0.0/12
        3. 192.168.0.0/16
5. Click Management Groups
6. Confirm that Jumphost and On-Prem Mgmt-Net exist and are properly populated
7. Click Add Group
8. Define the following Management Group
   1. RFC 1918
      • Group Name: RFC1918
      • Group Type: IP Address
      • Members:
        1. 10.0.0.0/8
        2. 172.16.0.0/12
        3. 192.168.0.0/16

9. Click Gateway Firewall
10. Add/Modify the following Compute Gateway Firewall rules

11. Publish the rule
12. Click Management Gateway
13. Confirm the On-Prem to vCenter rule exists and is defined appropriately
14. Add a rule to allow access from the Pods. Define the rule as follows:
    • Name: Internal to vCenter
    • Source: RFC1918
    • Destination: vCenter
    • Services: HTTPS, SSO
15. Publish the rule

16. Click DNS
17. Click the 3 vertical dots next to Management Gateway DNS Forwarder
18. Click Edit
19. Set Server IP 1 to 10.10.6.50
20. Clear Server IP 2
21. Click Save

1. In the SDDC Console, Click Open vCenter
2. Copy the CloudAdmin Password
3. Log into vCenter as:
   • Username: [email protected]
   • Password: {Paste-in-Copied-Password}
4. Click the Hamburger Menu --> Administration
5. In the Left pane under Single Sign-on, click Configuration
6. Click the Identity Sources tab
7. Click Add to add the On-Premises AD as an Identity Source using the values below
   • Identity Source name: 27 Virtual
   • Base Distinguished name for Users: dc=27virtual,dc=net
   • Base Distinguished name for Groups: dc=27virtual,dc=net
   • Domain Name: 27virtual.net
   • Domain Alias: 27Virtual
   • Username: [email protected]
   • Password: VMwareNinja1!
   • Primary Server URL: ldap://10.10.6.50
8. Click Add

9. Click Global Permissions
10. Click Add
11. Add and assign a user the CloudGlobalAdmin role by choosing the following:
    • Domain: 27virtual.net
    • User/Group: vmcexpert#-users (i.e. vmcexpert3-users)
    • Role: CloudGlobalAdmin
    • Click Propagate to children

12. Click the Hamburger Menu --> Inventory
13. Select the vCenter Server --> Permissions Tab
14. Click Add
15. Add and assign a user the CloudAdmin role by choosing the following:
    • Domain: 27virtual.net
    • User/Group: vmcexpert#-users (i.e. vmcexpert3-users)
    • Role: CloudAdmin
    • Click Propagate to children

1. In vCenter click The Hamburger Menu --> Workload Management
2. Click Create Namespace
3. Select the Cluster (Cluster-1)
4. Name the namespace vmcexpert3-32
5. Click Create

6. Click Add Permission in the Permission tile
7. Add the associated user account by selecting the following:
   • Identity Source: 27virtual.net
   • User/Group Search: vmcexpert#-xx (i.e. vmcexpert3-01)
   • Role: Owner
8. Click OK

9. Click Add Storage in the Storage Tile
10. Select vSAN Default Storage Policy
11. Click OK
12. Click Add VM Class in the VM Service Tile
13. Select the following VM Classes
    • best-effort-medium
    • best-effort-small
    • best-effort-xsmall
14. Click OK