part of

the Complete

Solution and step by

step instructions.

Explanation:

To create a custom QoS profile to prioritize the traffic on the phoenix-VLAN segment and limit the

rate of ingress traffic, you need to follow these steps:

Log in to the NSX Manager UI with admin credentials. The default URL is https://.

Navigate to Networking > Segments > Switching Profiles and click Add Switching Profile. Select QoS

as the profile type.

Enter a name and an optional description for the QoS profile, such as phoenix-QoS.

In the Mode section, select Untrusted as the mode from the drop-down menu. This will allow you to

set a custom DSCP value for the outbound IP header of the traffic on the segment.

In the Priority section, enter 46 as the DSCP value. This will mark the traffic with Expedited

Forwarding (EF) per-hop behavior, which is typically used for high-priority applications such as voice

or video.

In the Class of Service section, enter 5 as the CoS value. This will map the DSCP value to a CoS value

that can be used by VLAN-based logical ports or physical switches to prioritize the traffic.

In the Ingress section, enter 1000000 as the Average Bandwidth in Kbps. This will limit the rate of

inbound traffic from the VMs to the logical network to 1 Mbps.

Optionally, you can also configure Peak Bandwidth and Burst Size settings for the ingress traffic,

which will allow some burst traffic above the average bandwidth limit for a short duration.

Click Save to create the QoS profile.

Navigate to Networking > Segments and select the phoenix-VLAN segment that you want to apply

the QoS profile to.

Click Actions > Apply Profile and select phoenix-QoS as the switching profile that you want to apply

to the segment.

Click Apply to apply the profile to the segment.

You have successfully created a custom QoS profile and applied it to the phoenix-VLAN segment.

part of

the Complete

Solution and step by

step instructions.

Explanation:

To deploy three layer 2 overlay-backed segments and one layer 2 VLAN-backed segment, you need to

follow these steps:

Log in to the NSX Manager UI with admin credentials. The default URL is https://.

Navigate to Networking > Segments and click Add Segment.

Enter a name for the segment, such as Web-01.

Select Tier-1 as the connectivity option and choose an existing tier-1 gateway from the drop-down

menu or create a new one by clicking New Tier-1 Gateway.

Enter the gateway IP address of the subnet in a CIDR format, such as 192.168.10.1/24.

Select an overlay transport zone from the drop-down menu, such as Overlay-TZ.

Optionally, you can configure advanced settings such as DHCP, Metadata Proxy, MAC Discovery, or

QoS for the segment by clicking Set Advanced Configs.

Click Save to create the segment.

Repeat steps 2 to 8 for the other two overlay-backed segments, such as App-01 and DB-01, with

different subnet addresses, such as 192.168.20.1/24 and 192.168.30.1/24.

To create a VLAN-backed segment, click Add Segment again and enter a name for the segment, such

as Legacy-01.

Select Tier-0 as the connectivity option and choose an existing tier-0 gateway from the drop-down

menu or create a new one by clicking New Tier-0 Gateway.

Enter the gateway IP address of the subnet in a CIDR format, such as 10.10.10.1/24.

Select a VLAN transport zone from the drop-down menu, such as VLAN-TZ, and enter the VLAN ID for

the segment, such as 100.

Optionally, you can configure advanced settings such as DHCP, Metadata Proxy, MAC Discovery, or

QoS for the segment by clicking Set Advanced Configs.

Click Save to create the segment.

To apply a segment security profile to block DHCP requests on the segments, navigate to Networking

> Segments > Segment Profiles and click Add Segment Profile.

Select Segment Security as the profile type and enter a name and an optional description for the

profile.

Toggle the Server Block and Server Block - IPv6 buttons to enable DHCP filtering for both IPv4 and

IPv6 traffic on the segments that use this profile.

Click Save to create the profile.

Navigate to Networking > Segments and select the segments that you want to apply the profile to.

Click Actions > Apply Profile and select the segment security profile that you created in step 18.

Click Apply to apply the profile to the selected segments.

You have successfully deployed three layer 2 overlay-backed segments and one layer 2 VLAN-backed

segment with DHCP filtering using NSX-T Manager UI.

part of

the Complete

Solution and step by

step instructions.

Explanation:

To troubleshoot the NSX IPSec VPN service that has been reported down, you need to follow these

steps:

Log in to the NSX Manager UI with admin credentials. The default URL is https://.

Navigate to Networking > VPN > IPSec VPN and select the IPSec VPN session that is down. You can

identify the session by its name, local endpoint, remote endpoint, and status.

Click Show IPSec Statistics and view the details of the IPSec VPN session failure. You can see the error

message, the tunnel state, the IKE and ESP status, and the statistics of the traffic sent and received.

Compare the configuration details of the IPSec VPN session with the expected configuration as

provided below. Check for any discrepancies or errors in the parameters such as local and remote

endpoints, local and remote networks, IKE and ESP profiles, etc.

If you find any configuration errors, click Actions > Edit and modify the parameters accordingly. Click

Save to apply the changes.

If you do not find any configuration errors, check the connectivity and firewall rules between the

local and remote endpoints. You can use ping or traceroute commands from the NSX Edge CLI to test

the connectivity. You can also use show service ipsec command to check the status of IPSec VPN

service on the NSX Edge.

If you find any connectivity or firewall issues, resolve them by adjusting the network settings or

firewall rules on the NSX Edge or the third-party device.

After resolving the issues, verify that the IPSec VPN session is up and running by refreshing the IPSec

VPN page on the NSX Manager UI. You can also use show service ipsec sp and show service ipsec sa

commands on the NSX Edge CLI to check the status of security policy and security association for the

IPSec VPN session.

part of

the Complete

Solution and step by

step instructions.

Explanation:

To create a logical load balancer for several web servers, you need to follow these steps:

Log in to the NSX Manager UI with admin credentials. The default URL is https://.

Navigate to Networking > Load Balancing > Load Balancers and click Add Load Balancer.

Enter a name and an optional description for the load balancer. Select the tier-1 gateway where you

want to attach the load balancer from the drop-down menu or create a new one by clicking New

Tier-1 Gateway. Click Save.

Navigate to Networking > Load Balancing > Application Profiles and click Add Application Profile.

Enter a name and an optional description for the application profile. Select HTTP as the application

type from the drop-down menu. Optionally, you can configure advanced settings such as persistence,

X-Forwarded-For, SSL offloading, etc., for the application profile. Click Save.

Navigate to Networking > Load Balancing > Monitors and click Add Monitor.

Enter a name and an optional description for the monitor. Select HTTP as the protocol from the drop-

down menu. Optionally, you can configure advanced settings such as interval, timeout, fall count, rise

count, etc., for the monitor. Click Save.

Navigate to Networking > Load Balancing > Server Pools and click Add Server Pool.

Enter a name and an optional description for the server pool. Select an existing application profile

from the drop-down menu or create a new one by clicking New Application Profile. Select an existing

monitor from the drop-down menu or create a new one by clicking New Monitor. Optionally, you can

configure advanced settings such as algorithm, SNAT translation mode, TCP multiplexing, etc., for the

server pool. Click Save.

Click Members > Set > Add Member and enter the IP address and port number of each web server

that you want to add to the server pool. For example, enter 192.168.10.10:80 and 192.168.10.11:80

for two web servers listening on port 80. Click Save and then Close.

Navigate to Networking > Load Balancing > Virtual Servers and click Add Virtual Server.

Enter a name and an optional description for the virtual server. Enter the IP address and port number

of the virtual server that will receive the client requests, such as 10.10.10.100:80. Select HTTP as the

service profile from the drop-down menu or create a new one by clicking New Service Profile. Select

an existing server pool from the drop-down menu or create a new one by clicking New Server Pool.

Optionally, you can configure advanced settings such as access log, connection limit, rate limit, etc.,

for the virtual server. Click Save.

You have successfully created a logical load balancer for several web servers using NSX-T Manager

UI.

part of

the Complete

Solution and step by

step instructions.

Explanation:

To troubleshoot the bridge configuration and restore access to the application, you need to follow

these steps:

Log in to the NSX Manager UI with admin credentials. The default URL is https://.

Navigate to Networking > Segments and select the overlay segment that is bridged to the VLAN-

backed port group. For example, select Web-01 segment that you created in Task 2.

Click Bridge > Set and verify the configuration details of the bridge. Check for any discrepancies or

errors in the parameters such as bridge name, bridge ID, VLAN ID, edge node, etc.

If you find any configuration errors, click Edit and modify the parameters accordingly. Click Save to

apply the changes.

If you do not find any configuration errors, check the connectivity and firewall rules between the

overlay segment and the VLAN-backed port group. You can use ping or traceroute commands from

the NSX Edge CLI or the vSphere Web Client to test the connectivity. You can also use show service

bridge command to check the status of the bridge service on the NSX Edge.

If you find any connectivity or firewall issues, resolve them by adjusting the network settings or

firewall rules on the NSX Edge or the vSphere Distributed Switch.

After resolving the issues, verify that the bridge is functioning and the Bridge-VM is responding to

ICMP requests from the main console. You can also check the MAC addresses learned by the bridge

on both sides of the network using show service bridge mac command on the NSX Edge CLI.

part of

the Complete

Solution and step by

step instructions.

Explanation:

To prepare a VMware NSX-T Data Center ESXi compute cluster infrastructure, you need to follow

these steps:

Log in to the NSX Manager UI with admin credentials. The default URL is https://.

Navigate to System > Fabric > Profiles > Transport Node Profiles and click Add Profile.

Enter a name and an optional description for the transport node profile.

In the Host Switches section, click Set and select N-VDS as the host switch type.

Enter a name for the N-VDS switch and select the mode as Standard or Enhanced Datapath,

depending on your requirements.

Select the transport zones that you want to associate with the N-VDS switch. You can select one

overlay transport zone and one or more VLAN transport zones.

Select an uplink profile from the drop-down menu or create a custom one by clicking New Uplink

Profile.

In the IP Assignment section, select Use IP Pool and choose an existing IP pool from the drop-down

menu or create a new one by clicking New IP Pool.

In the Physical NICs section, map the uplinks to the physical NICs on the host. For example, map

Uplink 1 to vmnic2 and Uplink 2 to vmnic3.

Click Apply and then click Save to create the transport node profile.

Navigate to System > Fabric > Nodes > Host Transport Nodes and click Add Host Transport Node.

Select vCenter Server as the compute manager and select the cluster that contains the two ESXi

servers that you want to prepare for NSX-T overlay and VLAN use.

Select the transport node profile that you created in the previous steps and click Next.

Review the configuration summary and click Finish to start the preparation process.

The preparation process may take some time to complete. You can monitor the progress and status

of the host transport nodes on the Host Transport Nodes page. Once the preparation is complete,

you will see two host transport nodes with a green status icon and a Connected state. You have

successfully prepared a VMware NSX-T Data Center ESXi compute cluster infrastructure using a

transport node profile.

part of

the Complete

Solution and step by

step instructions.

Explanation:

To configure the NSX backups for the environment, you need to follow these steps:

Verify that an SFTP server is available on the network and obtain SFTP fingerprint. You can use the

search_web("SFTP server availability") tool to find some information on how to set up and check an

SFTP server. You can also use the ssh-keyscan command to get the fingerprint of the SFTP server. For

example, ssh-keyscan -t ecdsa sftp_server will return the ECDSA key of the sftp_server. You can

compare this key with the one displayed on the NSX Manager UI when you configure the backup

settings.

Configure NSX Backups via NSX Appliance Backup. Log in to the NSX Manager UI with admin

credentials. The default URL is https://. Select System > Lifecycle

Management > Backup & Restore. Click Edit under the SFTP Server label to configure your SFTP

server. Enter the FQDN or IP address of the backup file server, such as 10.10.10.100. The protocol text

box is already filled in. SFTP is the only supported protocol. Change the default port if necessary. The

default TCP port is 22. In the Directory Path text box, enter the absolute directory path where the

backups will be stored, such as /dat

a. The directory must already exist and cannot be the root directory (/). Avoid using path drive letters

or spaces in directory names; they are not supported. In the Passphrase text box, enter a passphrase

that will be used to encrypt and decrypt the backup files, such as VMware1!. Click Save to create the

backup configuration.

Configure Scheduling Criteria. On the Backup & Restore page, click Edit under the Schedule label to

configure your backup schedule. Select Enabled from the drop-down menu to enable scheduled

backups. Select Daily from the Frequency drop-down menu to run backups once every 24 hours.

Select a time from the Time drop-down menu to specify when the backup will start, such as 12:00

AM. Select Enabled from the Additional Backup Trigger drop-down menu to run backups when there

are changes published to the NSX environment. Click Save to create the backup schedule.

Verify that a backup file has been created on the SFTP server. On the Backup & Restore page, click

Start Backup to run a manual backup and verify that it completes successfully. You should see a

message saying “Backup completed successfully”. You can also check the status and details of your

backups on this page, such as backup size, duration, and timestamp. Alternatively, you can log in to

your SFTP server and check if there is a backup file in your specified directory path, such as /data.

part of

the Complete

Solution and step by

step instructions.

Explanation:

To review CPU sensitivity and threshold values, you need to follow these steps:

Log in to the NSX Manager UI with admin credentials. The default URL is https://.

Navigate to System > Settings > System Settings > CPU and Memory Thresholds.

You will see the current values for CPU and memory thresholds for NSX Manager, NSX Controller, and

NSX Edge. These values determine the percentage of CPU and memory usage that will trigger an

alarm on the NSX Manager UI.

You can modify the default threshold values by clicking Edit and entering new values in the text

boxes. For example, you can increase the CPU threshold for NSX Manager from 80% to 90% to reduce

the number of alarms for high CPU usage. Click Save to apply the changes.

You can also view the historical data for CPU and memory usage for each component by clicking View

Usage History. You can select a time range and a granularity level to see the usage trends and

patterns over time

part of

the Complete

Solution and step by

step instructions.

Explanation:

To run the GET call in the API using Postman and save the output to the desktop to a text file called

API.txt, you need to follow these steps:

Open Postman and create a new request tab. Select GET as the method from the drop-down menu.

Enter the URL of the NSX-T Policy API endpoint for retrieving the BGP routing table, such as

https:///policy/api/v1/infra/tier-0s/vmc/routingtable?enforcement_point_path=/infra/sites/default/enforcement-points/vmc-enforcementpoint

Click the Authorization tab and select Basic Auth as the type from the drop-down menu. Enter your

NSX-T username and password in the Username and Password fields, such as admin and VMware1!.

Click Send to execute the request and view the response in the Body tab. You should see a JSON

object with the BGP routing table information, such as routes, next hops, prefixes, etc.

Click Save Response and select Save to a file from the drop-down menu. Enter API.txt as the file

name and choose Desktop as the location. Click Save to save the output to your desktop.

You have successfully run the GET call in the API using Postman and saved the output to your desktop

to a text file called API.txt.

Thank you for your visit.

part of

the Complete

Solution and step by

step instructions.

Explanation:

To deploy a new instance of NSX-T into an environment with two isolated tenants, you need to follow

these steps:

Log in to the NSX Manager UI with admin credentials. The default URL is https://.

Navigate to System > Fabric > Nodes > Edge Transport Nodes and click Add Edge VM.

Enter a name and an optional description for the edge VM. Select the compute manager, cluster, and

resource pool where you want to deploy the edge VM. Click Next.

Select the deployment size and form factor for the edge VM. For this task, you can select Medium as

the size and VM as the form factor. Click Next.

Select the datastore and folder where you want to store the edge VM files. Click Next.

Configure the management network settings for the edge VM. Enter a hostname, a management IP

address, a default gateway, a DNS server, and a domain search list. Optionally, you can enable SSH

and join the edge VM to a domain. Click Next.

Configure the transport network settings for the edge VM. Select an N-VDS as the host switch type

and enter a name for it. Select an uplink profile from the drop-down menu or create a new one by

clicking New Uplink Profile. Map the uplinks to the physical NICs on the edge VM. For example, map

Uplink 1 to fp-eth0 and Uplink 2 to fp-eth1. Optionally, you can configure IP assignment, MTU, or

LLDP for the uplinks. Click Next.

Review the configuration summary and click Finish to deploy the edge VM.

Repeat steps 2 to 8 to deploy another edge VM for redundancy.

Navigate to Networking > Tier-0 Gateway and click Add Gateway > VRF.

Enter a name and an optional description for the VRF gateway. Select an existing tier-0 gateway as

the parent gateway or create a new one by clicking New Tier-0 Gateway.

Click VRF Settings and enter a VRF ID for the tenant. Optionally, you can enable EVPN settings if you

want to use EVPN as the control plane protocol for VXLAN overlay networks.

Click Save to create the VRF gateway.

Repeat steps 10 to 13 to create another VRF gateway for the second tenant with a different VRF ID.

Navigate to Networking > Segments and click Add Segment.

Enter a name and an optional description for the segment. Select VLAN as the connectivity option

and enter a VLAN ID for the segment. For example, enter 128 for Tenant A’s first uplink VLAN

segment.

Select an existing transport zone from the drop-down menu or create a new one by clicking New

Transport Zone.

Click Save to create the segment.

Repeat steps 15 to 18 to create three more segments for Tenant A’s second uplink VLAN segment

(VLAN ID 129) and Tenant B’s uplink VLAN segments (VLAN ID 158 and 159).

Navigate to Networking > Tier-0 Gateway and select the VRF gateway that you created for Tenant A.

Click Interfaces > Set > Add Interface.

Enter a name and an optional description for the interface.

Enter the IP address and mask for the external interface in CIDR format, such as 10.10.10.1/24.

In Type, select External.

In Connected To (Segment), select the VLAN segment that you created for Tenant A’s first uplink

VLAN segment (VLAN ID 128).

Select an edge node where you want to attach the interface, such as Edge-01.

Enter the Access VLAN ID from the list as configured for the segment, such as 128.

Click Save and then Close.

Repeat steps 21 to 28 to create another interface for Tenant A’s second uplink VLAN segment (VLAN

ID 129) on another edge node, such as Edge-02.

Repeat steps 20 to 29 to create two interfaces for Tenant B’s uplink VLAN segments (VLAN ID 158 and

159) on each edge node using their respective VRF gateway and IP addresses.

Configure BGP on each VRF gateway using NSX UI or CLI commands12. You need to specify the local

AS number, remote AS number, BGP neighbors, route redistribution, route filters, timers,

authentication, graceful restart, etc., according to your requirements34.

Configure BGP on each physical router using their respective CLI commands56. You need to specify

similar parameters as in step 31 and ensure that they match with their corresponding VRF gateway

settings78.

Verify that BGP sessions are established between each VRF gateway and its physical router neighbors

using NSX UI or CLI commands . You can also check the routing tables and BGP statistics on each

device .

You have successfully deployed a new instance of NSX-T into an environment with two isolated

tenants using VRF Lite and BGP.