3V0-41-22 Practice Questions

part of

the Complete

Solution and step by

step instructions.

Explanation:

To enable logging for the production NSX-T environment, you need to follow these steps:

Verify via putty with SSH that the administrator can connect to all NSX-Transport Nodes. You can use

the credentials identified in Putty (admin) to log in to each transport node. For example, you can use

the following command to connect to the sfo01w01en01 edge transport node: ssh

admin@sfo01w01en01. You should see a welcome message and a prompt to enter commands.

Verify that there is no current active logging enabled by reviewing that directory is empty -

/var/log/syslog-. You can use the ls command to list the files in the /var/log/syslog directory. For

example, you can use the following command to check the sfo01w01en01 edge transport node: ls

/var/log/syslog. You should see an empty output if there is no active logging enabled.

Enable NSX Manager Cluster logging. You can use the search_web("NSX Manager Cluster logging

configuration") tool to find some information on how to configure remote logging for NSX Manager

Cluster. One of the results is NSX-T Syslog Configuration Revisited - vDives, which provides the

following steps:

Navigate to System > Fabric > Profiles > Node Profiles then select All NSX Nodes then under Syslog

Servers click +ADD

Enter the IP or FQDN of the syslog server, the Port and Protocol and the desired Log Level then click

ADD

Select multiple configuration choices that could be appropriate success criteri

a. You can use the search_web("NSX-T logging success criteria") tool to find some information on

how to verify and troubleshoot logging for NSX-T. Some of the possible success criteria are:

The syslog server receives log messages from all NSX nodes

The log messages contain relevant information such as timestamp, hostname, facility, severity,

message ID, and message content

The log messages are formatted and filtered according to the configured settings

The log messages are encrypted and authenticated if using secure protocols such as TLS or LI-TLS

Enable NSX Edge Node logging. You can use the search_web("NSX Edge Node logging configuration")

tool to find some information on how to configure remote logging for NSX Edge Node. One of the

results is Configure Remote Logging - VMware Docs, which provides the following steps:

Run the following command to configure a log server and the types of messages to send to the log

server. Multiple facilities or message IDs can be specified as a comma delimited list, without spaces.

set logging-server proto level [facility ]

[messageid ] [serverca ] [clientca ] [certificate ] [key

] [structured-data ]

Validate logs are generated on each selected appliance by reviewing the "/var/log/syslog”. You can

use the cat or tail commands to view the contents of the /var/log/syslog file on each appliance. For

example, you can use the following command to view the last 10 lines of the sfo01w01en01 edge

transport node: tail -n 10 /var/log/syslog. You should see log messages similar to this:

2023-04-06T12:34:56+00:00 sfo01w01en01 user.info nsx-edge[1234]: 2023-04-06T12:34:56Z nsx-

edge[1234]: INFO: [nsx@6876 comp="nsx-edge" subcomp="nsx-edge" level="INFO"

security="False"] Message from nsx-edge

You have successfully enabled logging for the production NSX-T environment.

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 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 troubleshoot ICMP traffic and make any necessary changes to the Boston application security

policy, you need to follow these steps:

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

Navigate to Security > Distributed Firewall and select the firewall policy that applies to the Boston

application. For example, select Boston-web-Application.

Click Show IPSec Statistics and view the details of the firewall rule hits and logs. You can see which

rules are matching the ICMP traffic and which actions are taken by the firewall.

If you find that the ICMP traffic is allowed by a rule that is not intended for it, you can edit the rule

and change the action to Drop or Reject. You can also modify the source, destination, or service

criteria of the rule to make it more specific or exclude the ICMP traffic.

If you find that the ICMP traffic is not matched by any rule, you can create a new rule and specify the

action as Drop or Reject. You can also specify the source, destination, or service criteria of the rule to

match only the ICMP traffic from the main console to the Boston web VMs.

After making the changes, click Publish to apply the firewall policy.

Verify that the ICMP traffic is blocked by pinging the Boston web VMs from the main console again.

You should see a message saying “Request timed out” or “Destination unreachable”.

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 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.

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 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 troubleshoot why the Tampa web servers cannot communicate to any northbound networks, you

need to follow these steps:

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

Navigate to Networking > Tier-0 Gateway and select the tier-0 gateway that connects the NSX-T

network segment to the northbound networks. For example, select T0-GW-01.

Click Interfaces > Set and verify the configuration details of the interfaces. Check for any

discrepancies or errors in the parameters such as IP address, subnet mask, MTU, 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 tier-

0 gateway and the northbound networks. 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 router

command to check the status of the routing 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 northbound devices.

After resolving the issues, verify that the Tampa web servers can communicate to any northbound

networks by pinging the Control Center @ 192.168.110.10 from one of the web servers.

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.