VMware 2V0-41.23 - VMware NSX 4.x Professional

https://docs.vmware.com/en/VMware-Validated-Design/5.0.1/com.vmware.vvd.sddc-nsxt-domain-deploy.doc/GUID-B7019BCE-4FA1-40BB-8DC2-EE47967A47F1.html

You can replace the certificate for a manager node or the manager cluster virtual IP (VIP) by making an API call: • To replace the certificate of a manager node, use the POST API call: https:// /api/v1/node/services/http?action=apply_certificate&certificate_id= • To replace the certificate of the manager cluster VIP, use the POST API call: https:// /api/v1/cluster/api-certificate?action=set_cluster_certificate&certificate_id=

According to the VMware NSX Documentation, these are the two places where you need to configure the VLANs used in VRF Lite:

Uplink trunk segment: This is a segment that connects a tier-0 gateway to a physical network using multiple VLAN tags. You need to configure the VLAN IDs for each VRF on this segment.

Uplink interface of the VRF gateway: This is an interface that connects a VRF gateway to an uplink trunk segment using a specific VLAN tag. You need to configure the VLAN ID for each VRF on this interface.

Distributed Firewall on VDS is a feature of NSX-T Data Center that allows users to install Distributed Security for vSphere Distributed Switch (VDS) without the need to deploy an NSX Virtual Distributed Switch (N-VDS). This feature provides NSX security capabilities such as Distributed Firewall (DFW), Distributed IDS/IPS, Identity Firewall, L7 App ID, FQDN Filtering, NSX Intelligence, and NSX Malware Prevention. To enable this feature, the following requirements must be met in the environment:

The NSX version must be 3.2 and later1. This is the minimum version that supports Distributed Security for VDS.

The VDS version must be 6.6.0 and later1. This is the minimum version that supports the NSX host preparation operation that activates the DFW with the default rule set to allow.

References:

Overview of NSX IDS/IPS and NSX Malware Prevention

The Traceflow tool identifies issues in a network by injecting synthetic traffic into the data plane and observing the results in the control plane. This allows the tool to identify any issues in the network and provide a detailed report on the problem. You can use the Traceflow tool to test connectivity between any two endpoints in your NSX-T Data Center environment.

L2 VPN is a feature of NSX that allows extending Layer 2 networks across different sites or clouds over an IPsec tunnel. L2 VPN has an advantage of enabling VM mobility with re-IP, which means that VMs can be moved from one site to another without changing their IP addresses or network configurations. This is possible because L2 VPN allows both sites to use the same broadcast domain, which means that they share the same subnet and VLAN .

BGP will be configured on the T0 SR. Connect to the VRF for the T0 SR and run get bgp neighbor once connected to it. https://docs.vmware.com/en/VMware-Validated-Design/5.1/sddc-deployment-of-vmware-nsx-t-workload-domains-with-multiple-availability-zones/GUID-8BD4228A-75C6-4C60-80B4-538D4297E11A.html

For the BGP configuration on NSX-T, the Tier-0 Service Router (SR) is typically where BGP is configured. To check the BGP neighbor status:

Connect to the VRF for the T0 SR, which is VRF 3 based on the provided output.

Run the command to get BGP neighbor status once connected to it.

Management Plane Appliance Proxy Hub (MP APH) to host connectivity - TCP:1234 Central Control Plane (CCP) to host (NSX-Proxy) connectivity - TCP: 1235 esxcli network ip connection list | grep 1234 is the correct answer. https://docs.vmware.com/en/VMware- NSX/4.1/administration/GUID-7F899902-6884-40D0-B0AF-DF713AB052BD.html?hWord=N4IghgNiBcIHYGcAeACADgewE4BcUEYAmAZgBYQBfIA

The two interfaces that will be used for ingress traffic on the Edge node supporting a Single Tier topology are:

B. Tier-0 Uplink interface

C. Downlink Interface for the Tier-0 DR

The Tier-0 Uplink interface is the interface that connects the Tier-0 gateway to the external network. It is used to receive traffic from the physical router or switch that is the next hop for the Tier-0 gateway. The Tier-0 Uplink interface can be configured with a static IP address or use BGP to exchange routes with the external network.

The Downlink Interface for the Tier-0 DR is the interface that connects the Tier-0 gateway to the workload segments. It is used to receive traffic from the VMs or containers that are attached to the segments. The Downlink Interface for the Tier-0 DR is a logical interface (LIF) that is distributed across all transport nodes that host the segments. The Downlink Interface for the Tier-0 DR has an IP address that acts as the default gateway for the VMs or containers on the segments.

According to the VMware NSX Documentation1, NSX-T Data Center supports the following types of DHCP configuration on a segment:

Local DHCP server: This option creates a local DHCP server that has an IP address on the segment and provides dynamic IP assignment service only to the VMs that are attached to the segment.

Gateway DHCP server: This option is attached to a tier-0 or tier-1 gateway and provides DHCP service to the networks (overlay segments) that are directly connected to the gateway and configured to use a gateway DHCP server.

DHCP Relay: This option relays the DHCP client requests to the external DHCP servers that can be in any subnet, outside the SDDC, or in the physical network.

https://docs.vmware.com/en/VMware-NSX/4.0/administration/GUID-486C1281-C6CF-47EC-B2A2-0ECFCC4A68CE.html