3V0-41.22 Exam Questions & Answers

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.

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.

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.

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

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://<nsx-manager-ip-address>/policy/api/v1/infra/tier-0s/vmc/routing-table?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.