VMware 3V0-41.22 Advanced Deploy VMware NSX-T Data Center 3.x Exam Practice Test

Answer : A

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 <hostname-or-ip-address [:port]> 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 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.

Answer : A

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://<nsx-manager-ip-address>.

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.

Answer : A

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://<nsx-manager-ip-address>.

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.

Answer : A

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://<nsx-manager-ip-address>.

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.

Answer : A

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.

Answer : A

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://<nsx-manager-ip-address>.

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.

Answer : A

Step-by-Step Guide

Creating Tags and Security Groups

First, log into the NSX-T Manager GUI and navigate to Inventory > Tags to create tags like 'BOSTON-Web' for web servers and assign virtual machines such as BOSTON-web-01a and BOSTON-web-02

a. Repeat for 'BOSTON-App' and 'BOSTON-DB' with their respective VMs. Then, under Security > Groups, create security groups (e.g., 'BOSTON Web-Servers') based on these tags to organize the network logically.

Excluding Virtual Machines

Next, go to Security > Distributed Firewall > Exclusion List and add the 'core-A' virtual machine to exclude it from firewall rules, ensuring it operates without distributed firewall restrictions.

Defining Custom Services

Check Security > Services for existing services. If 'TCP-9443' and 'TCP-3051' are missing, create them by adding new services with the protocol TCP and respective port numbers to handle specific application traffic.

Setting Up the Policy and Rules

Create a new policy named 'BOSTON-Web-Application' under Security > Distributed Firewall > Policies. Add rules within this policy:

Allow any source to 'BOSTON Web-Servers' for HTTP/HTTPS.

Permit 'BOSTON Web-Servers' to 'BOSTON App-Servers' on TCP-9443.

Allow 'BOSTON App-Servers' to 'BOSTON DB-Servers' on TCP-3051. Finally, save and publish the policy to apply the changes.

This setup ensures secure, segmented traffic for the 3-tier web application, an unexpected detail being the need to manually create custom services for specific ports, enhancing flexibility.

Survey Note: Detailed Configuration of Micro-Segmentation Policy in VMware NSX-T Data Center 3.x

This note provides a comprehensive guide for configuring a micro-segmentation policy for a 3-tier web application in VMware NSX-T Data Center 3.x, based on the task requirements. The process involves creating tags, security groups, excluding specific virtual machines, defining custom services, and setting up distributed firewall policies. The following sections detail each step, ensuring a thorough understanding for network administrators and security professionals.

Background and Context

Micro-segmentation in VMware NSX-T Data Center is a network security technique that logically divides the data center into distinct security segments, down to the individual workload level, using network virtualization technology. This is particularly crucial for a 3-tier web application, comprising web, application, and database layers, to control traffic and enhance security. The task specifies configuring this for a production environment, with notes indicating passwords are in user_readme.txt and no need to wait for configuration changes, as processing may take time.

Step-by-Step Configuration Process

Step 1: Creating Tags

Tags are used in NSX-T to categorize virtual machines, which can then be grouped for policy application. The process begins by logging into the NSX-T Manager GUI, accessible via a web browser with admin privileges. Navigate to Inventory > Tags, and click 'Add Tag' to create the following:

Tag name: 'BOSTON-Web', assigned to virtual machines BOSTON-web-01a and BOSTON-web-02a.

Tag name: 'BOSTON-App', assigned to BOSTON-app-01a.

Tag name: 'BOSTON-DB', assigned to BOSTON-db-01a.

This step ensures each tier of the application is tagged for easy identification and grouping, aligning with the attachment's configuration details.

Step 2: Creating Security Groups

Security groups in NSX-T are logical constructs that define membership based on criteria like tags, enabling targeted policy application. Under Security > Groups, click 'Add Group' to create:

Group name: 'BOSTON Web-Servers', with criteria set to include the 'BOSTON-Web' tag.

Group name: 'BOSTON App-Servers', with criteria set to include the 'BOSTON-App' tag.

Group name: 'BOSTON DB-Servers', with criteria set to include the 'BOSTON-DB' tag.

This step organizes the network into manageable segments, facilitating the application of firewall rules to specific tiers.

Step 3: Excluding 'core-A' VM from Distributed Firewall

The distributed firewall (DFW) in NSX-T monitors east-west traffic between virtual machines. However, certain VMs, like load balancers or firewalls, may need exclusion to operate without DFW restrictions. Navigate to Security > Distributed Firewall > Exclusion List, click 'Add', select 'Virtual Machine', and choose 'core-A'. Click 'Save' to exclude it, ensuring it bypasses DFW rules, as per the task's requirement.

Step 4: Defining Custom Services

Firewall rules often require specific services, which may not be predefined. Under Security > Services, check for existing services 'TCP-9443' and 'TCP-3051'. If absent, create them:

Click 'Add Service', name it 'TCP-9443', set protocol to TCP, and port to 9443.

Repeat for 'TCP-3051', with protocol TCP and port 3051.

This step is crucial for handling application-specific traffic, such as the TCP ports mentioned in the policy type (TCP-9443, TCP-3051), ensuring the rules can reference these services.

Step 5: Creating the Policy and Rules

The final step involves creating a distributed firewall policy to enforce micro-segmentation. Navigate to Security > Distributed Firewall > Policies, click 'Add Policy', and name it 'BOSTON-Web-Application'. Add a section, then create the following rules:

Rule Name: 'Any-to-Web'

Source: Any (select 'Any' or IP Address 0.0.0.0/0)

Destination: 'BOSTON Web-Servers' (select the group)

Service: HTTP/HTTPS (predefined service)

Action: Allow

Rule Name: 'Web-to-App'

Source: 'BOSTON Web-Servers'

Destination: 'BOSTON App-Servers'

Service: TCP-9443 (custom service created earlier)

Action: Allow

Rule Name: 'App-to-DB'

Source: 'BOSTON App-Servers'

Destination: 'BOSTON DB-Servers'

Service: TCP-3051 (custom service created earlier)

Action: Allow

After defining the rules, click 'Save' and 'Publish' to apply the policy. This ensures traffic flows as required: any to web servers for HTTP/HTTPS, web to app on TCP-9443, and app to database on TCP-3051, while maintaining security through segmentation.

Additional Considerations

The task notes indicate no need to wait for configuration changes, as processing may take time, and steps are not dependent, suggesting immediate progression is acceptable. Passwords are in user_readme.txt, implying the user has necessary credentials. The policy order is critical, with rules processed top-to-bottom, and the attachment's 'Type: TCP-9443, TCP-3051' likely describes the services used, not affecting the configuration steps directly.

Table: Summary of Configuration Details

Component

Details

Tags

BOSTON-Web (BOSTON-web-01a, BOSTON-web-02a), BOSTON-App (BOSTON-app-01a), BOSTON-DB (BOSTON-db-01a)

Security Groups

BOSTON Web-Servers (tag BOSTON-Web), BOSTON App-Servers (tag BOSTON-App), BOSTON DB-Servers (tag BOSTON-DB)

DFW Exclusion List

Virtual Machine: core-A

Custom Services

TCP-9443 (TCP, port 9443), TCP-3051 (TCP, port 3051)

Policy Name

BOSTON-Web-Application

Firewall Rules

Any-to-Web (Any to Web-Servers, HTTP/HTTPS, Allow), Web-to-App (Web to App-Servers, TCP-9443, Allow), App-to-DB (App to DB-Servers, TCP-3051, Allow)

This table summarizes the configuration, aiding in verification and documentation.

Unexpected Detail

An unexpected aspect is the need to manually create custom services for TCP-9443 and TCP-3051, which may not be predefined, highlighting the flexibility of NSX-T for application-specific security policies.

Conclusion

This detailed process ensures a robust micro-segmentation policy, securing the 3-tier web application by controlling traffic between tiers and excluding specific VMs from DFW, aligning with best practices for network security in VMware NSX-T Data Center 3.x.