To configure traffic replication to the monitoring software for your Tampa web overlay segments with bi-directional 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 and select the Tampa web overlay segment that you want to replicate the traffic from. For example, select Web-01 segment that you created in Task 2.
• Click Port Mirroring > Set > Add Session and enter a name and an optional description for the port mirroring session. For example, enter Tampa-Web-Monitoring.
• In the Direction section, select Bi-directional as the direction from the drop-down menu. This will replicate both ingress and egress traffic from the source to the destination.
• In the Source section, click Set and select the VMs or logical ports that you want to use as the source of the traffic. For example, select Web-VM-01 and Web-VM-02 as the source VMs. Click Apply.
• In the Destination section, click Set and select Remote L3 SPAN as the destination type from the drop-down menu. This will allow you to replicate the traffic to a remote destination outside of the NSX-T environment.
• Enter the IP address of the destination device where you have installed the network monitoring software, such as 10.10.10.200.
• Select an existing service profile from the drop-down menu or create a new one by clicking New Service Profile. A service profile defines the encapsulation type and other parameters for the replicated traffic.
• Optionally, you can configure advanced settings such as TCP/IP stack, snap length, etc., for the port mirroring session.
• Click Save and then Close to create the port mirroring session.

You have successfully configured traffic replication to the monitoring software for your Tampa web overlay segments with bi-directional traffic using NSX-T Manager UI.

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.

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

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.