VMware 3V0-41.22 問題集

質問 1：
Task 15
You have been asked to enable logging so that the global operations team can view inv Realize Log Insight that their Service Level Agreements are being met for all network traffic that is going in and out of the NSX environment. This NSX environment is an Active / Active two Data Center design utilizing N-VDSwith BCP.
You need to ensure successful logging for the production NSX-T environment.
You need to:
Verify via putty with SSH that the administrator can connect to all NSX-Transport Nodes. You will use the credentials identified in Putty (admin).
Verify that there is no current active logging enabled by reviewing that directory is empty -/var/log/syslog-
Enable NSX Manager Cluster logging
Select multiple configuration choices that could be appropriate success criteria Enable NSX Edge Node logging Validate logs are generated on each selected appliance by reviewing the "/var/log/syslog" Complete the requested task.
Notes: Passwords are contained in the user _ readme.txt. complete.
These task steps are dependent on one another. This task should take approximately 10 minutes to complete.
正解：
See the Explanation 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 thelscommand 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 thesearch_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 isNSX-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 criteria. You can use thesearch_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 thesearch_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 isConfigure 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 <hostname-or-ip-address [:port]> proto <proto> level <level> [facility <facility>]
[messageid <messageid>] [serverca <filename>] [clientca <filename>] [certificate <filename>] [key
<filename>] [structured-data <structured-data>]
Validate logs are generated on each selected appliance by reviewing the "/var/log/syslog". You can use thecatortailcommands 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.

質問 2：
Task 7
you are asked 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:
* Create a custom QoS profile for the phoenix-VLAN using the following configuration detail:

* Apply the profile on the 'phoenix-VLAN' segment
Complete the requested task.
Notes: Passwords are contained in the user_readme.txt.
take approximately 5 minutes to complete.
Subsequent tasks may require the completion of this task.
This task should See the Explanation 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://<nsx-manager-ip-address>.
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.