Free VMware 3V0-643 Practice Test & Real Exam Questions
An NSX administrator has been troubleshooting a communication issue between Edge device TS-Comm-Edge-01 and the TS-Comm-DLR-01 logical router with no success and has reached out to you for further assistance. The following troubleshooting has already been performed.
Temporarily disabled the firewall between both devices.
Unsuccessful ping from TS-Comm-Edge-01 to TS-Comm-DLR-01
Unsuccessful ping from TS-Comm-DLR-01 to TS-Comm-Edge-01
Determine and resolve the communication issue between the two devices.
Requirements:
vCenter: vcsa01a.crop.local
Credentials: [email protected] / VMware1!
Troubleshooting Information:
Edge: TS-Comm-Edge-01 (192.168.33.1)
DLR: TS-Comm-DLR-01 (192.168.33.8)
Transit Network: TS-Comm-Transit
IP Subnet: 192.168.33.0/29
Ensure communication between both devices is successful.
NOTE:
IP addresses must remain unchanged.
HOL LAB for Practice:
See the explanation part for complete solution.
Temporarily disabled the firewall between both devices.
Unsuccessful ping from TS-Comm-Edge-01 to TS-Comm-DLR-01
Unsuccessful ping from TS-Comm-DLR-01 to TS-Comm-Edge-01
Determine and resolve the communication issue between the two devices.
Requirements:
vCenter: vcsa01a.crop.local
Credentials: [email protected] / VMware1!
Troubleshooting Information:
Edge: TS-Comm-Edge-01 (192.168.33.1)
DLR: TS-Comm-DLR-01 (192.168.33.8)
Transit Network: TS-Comm-Transit
IP Subnet: 192.168.33.0/29
Ensure communication between both devices is successful.
NOTE:
IP addresses must remain unchanged.
HOL LAB for Practice:
See the explanation part for complete solution.
Correct Answer:
SOLUTION:
Troubleshooting:
TS-Comm-Edge-01
Interfaces -> TS-Comm-Transit (change the subnet mask to 28)
Verification:
SSH to TS-Comm-Edge-01 (192.168.7.2) and ping 192.168.33.8
(2) select Ts-Comm-DLR-01 from Nsx Edge. select Manage tab. select Settings.
select interface. check the ip address and mask. and change the mask to /28.
click ok.
(3) select Manage Tab. select Routing. select global configuration. click edit.
select OSPF enter router ID 192.168.33.8 click ok. click on enable
click on publish changes.
(4) select OSPF. click edit. enable OSPF. Enter Protocol Address 192.168.33.7 enter forwarding address 192.168.33.8 (ip address of the vnic). click enable graceful restart. click ok.
(5) under area. click + Sign and add area 0. select type normal. select authentication none. click ok.
(6) under area to interface mapping. click on + sign. select interface uplink enter area 0. enter hello interval 10. dear interval 40. enter priority 128 enter cost 1. click ok. click publish changes.
(7) select TS-Comm-Edge-01. select manage select routing. select global configuration.
click edit under dynamic routing configuration.enter router id ts-comm 192.168.33.
click ok. click publish changes.
(8) select OSPF. click edit. enable OSPF. enable graceful restart. click ok.
select vnic transit. enter area 0. click on blue icon. change the subnet mastk to /28. click ok.
(9) select Firewall under manage Tab. click disable. click publish changes.
do the same steps for Ts-comm-DLR-01. and disable the firewall.
Troubleshooting:
TS-Comm-Edge-01
Interfaces -> TS-Comm-Transit (change the subnet mask to 28)
Verification:
SSH to TS-Comm-Edge-01 (192.168.7.2) and ping 192.168.33.8
(2) select Ts-Comm-DLR-01 from Nsx Edge. select Manage tab. select Settings.
select interface. check the ip address and mask. and change the mask to /28.
click ok.
(3) select Manage Tab. select Routing. select global configuration. click edit.
select OSPF enter router ID 192.168.33.8 click ok. click on enable
click on publish changes.
(4) select OSPF. click edit. enable OSPF. Enter Protocol Address 192.168.33.7 enter forwarding address 192.168.33.8 (ip address of the vnic). click enable graceful restart. click ok.
(5) under area. click + Sign and add area 0. select type normal. select authentication none. click ok.
(6) under area to interface mapping. click on + sign. select interface uplink enter area 0. enter hello interval 10. dear interval 40. enter priority 128 enter cost 1. click ok. click publish changes.
(7) select TS-Comm-Edge-01. select manage select routing. select global configuration.
click edit under dynamic routing configuration.enter router id ts-comm 192.168.33.
click ok. click publish changes.
(8) select OSPF. click edit. enable OSPF. enable graceful restart. click ok.
select vnic transit. enter area 0. click on blue icon. change the subnet mastk to /28. click ok.
(9) select Firewall under manage Tab. click disable. click publish changes.
do the same steps for Ts-comm-DLR-01. and disable the firewall.
Management requires you to build a new logical topology for a new application that will include a hardware search appliance (HAS). The new application must contain a web tier and database tier on separate IP domains. Use the existing App01-DLR to complete the task.
Requirements:
vCenter: vcsa-01.corp.local
Credentials: [email protected] / VMware1!
vDS: vds-mgt-edge-a
Existing DLR Name: App01-DLR
New object prefix - App01
New object suffic - New
Create a new distributed port group for this task named vds-HSA-NEW.
The HAS must reside on the same IP subnet as the database.
The new application must contain a web tier and database tier on separate domains to be used at a future date.
Once deployed the HAS will be connected to a network with VLAN ID 500.
The proper physical switch ports for the uplinks have already been trunked to include VLAN 500.
VLANs configured in the compute racks are isolated to a single rack.
Any objects/items created must be named with a prefix of App01 and a suffix containing their function with NEW (for example: App01-Function-NEW) NOTE:
The hardware appliance and application virtual machines have not been deployed. Attempts to connectivity to the appliance will not succeed.
HOL LAB for Practice:
Bridging and other questions 7, 8, 9 and LAB - HOL-1925-02 Module 1
See the explanation part for complete solution.
Requirements:
vCenter: vcsa-01.corp.local
Credentials: [email protected] / VMware1!
vDS: vds-mgt-edge-a
Existing DLR Name: App01-DLR
New object prefix - App01
New object suffic - New
Create a new distributed port group for this task named vds-HSA-NEW.
The HAS must reside on the same IP subnet as the database.
The new application must contain a web tier and database tier on separate domains to be used at a future date.
Once deployed the HAS will be connected to a network with VLAN ID 500.
The proper physical switch ports for the uplinks have already been trunked to include VLAN 500.
VLANs configured in the compute racks are isolated to a single rack.
Any objects/items created must be named with a prefix of App01 and a suffix containing their function with NEW (for example: App01-Function-NEW) NOTE:
The hardware appliance and application virtual machines have not been deployed. Attempts to connectivity to the appliance will not succeed.
HOL LAB for Practice:
Bridging and other questions 7, 8, 9 and LAB - HOL-1925-02 Module 1
See the explanation part for complete solution.
Correct Answer:
SOLUTION:
Step 1: From SiteA vCenter web client -> Networking -> Data Center SiteA -> create a new distribution port group named vds-HAS-NEW with VLAN ID 500 in vds-mgmt-edge.
Create LS on 192.168.110.15 = App01-WebTier-NEW
Create LS on 192.168.110.15 = App01-DBTier-NEW
NSX Edges -> App01-DLR
8) got NsX Edge and select App01-DLR. select Manage, select settings and click on + Sign (9) Enter interface name App01-Web-New, select type internal. select App01-Webtier-New LS Enter ip address 192.168.1.1/24. repeat the same steps for App01-DBtier-New but take ip addres
192.168.2.1 /24
Name: App01-Bridge-NEW
Logical Switch: App01-DBTier-NEW
Distributed Port Group: vds-HAS-NEW
(11) be sure under App01-DB-New the bridging is enable.
Step 1: From SiteA vCenter web client -> Networking -> Data Center SiteA -> create a new distribution port group named vds-HAS-NEW with VLAN ID 500 in vds-mgmt-edge.
Create LS on 192.168.110.15 = App01-WebTier-NEW
Create LS on 192.168.110.15 = App01-DBTier-NEW
NSX Edges -> App01-DLR
8) got NsX Edge and select App01-DLR. select Manage, select settings and click on + Sign (9) Enter interface name App01-Web-New, select type internal. select App01-Webtier-New LS Enter ip address 192.168.1.1/24. repeat the same steps for App01-DBtier-New but take ip addres
192.168.2.1 /24
Name: App01-Bridge-NEW
Logical Switch: App01-DBTier-NEW
Distributed Port Group: vds-HAS-NEW
(11) be sure under App01-DB-New the bridging is enable.
Configure a solution that extends an IP subnet between two data centers. The solution must ensure secure communication between two data centers. A standalone Edge Appliance has already been deployed and preconfigured in Site-B on the Compute Cluster.
Requirements:
vCenter: vcsa-01a.corp.local
Credentials: [email protected] / VMware1!
HQ Site Information:
Edge: Preimeter-Gateway-01
Logical Segment: Extend-LS-01
Connected to: vds-mgt-a_Trunk_Network
VPN Server settings: 192.168.100.3
Use the system generated certificate.
Preconfigured Standalone Edge Appliance: NSX l2vpn
Edge: 192.168.200.5
L2VPN Server Information:
Name: Peer-Site-NEW
Trunk ID = 10
User ID = peeruser1
Password = VMware1!
Encryption = AES256-SHA
The solution must ensure secure communication between the data centers.
NOTE:
No virtual machines are attached to the Logical switch Application-Tier-01, so there is no need to test communication across the tunnel.
Ensure that L2VPN server statistics shows Tunnel status of UP.
HOL LAB for Practice:
L2VPN and other questions 7, 8, 9
See the explanation part for complete solution.
Requirements:
vCenter: vcsa-01a.corp.local
Credentials: [email protected] / VMware1!
HQ Site Information:
Edge: Preimeter-Gateway-01
Logical Segment: Extend-LS-01
Connected to: vds-mgt-a_Trunk_Network
VPN Server settings: 192.168.100.3
Use the system generated certificate.
Preconfigured Standalone Edge Appliance: NSX l2vpn
Edge: 192.168.200.5
L2VPN Server Information:
Name: Peer-Site-NEW
Trunk ID = 10
User ID = peeruser1
Password = VMware1!
Encryption = AES256-SHA
The solution must ensure secure communication between the data centers.
NOTE:
No virtual machines are attached to the Logical switch Application-Tier-01, so there is no need to test communication across the tunnel.
Ensure that L2VPN server statistics shows Tunnel status of UP.
HOL LAB for Practice:
L2VPN and other questions 7, 8, 9
See the explanation part for complete solution.
Correct Answer:
SOLUTION:
Add new Logical Switch: "Application-Tier-01"
NSX Edges -> Perimeter-Gateway-01 -> Manage -> Settings -> Interfaces -> edit vNIC4
Name: Extend-LS-01
Type: Trunk
Connected To:
Distributed Portgroup: vds-mgmt-a_trunknetwork
Add Sub Interface:
L2VPN Settings:
( select VPN under manage and enable L2VPN. click publish changes..
Then below
In actual exam, encryption is = AES256-SHA
(8) go to Vcenter b select datacenter - b. select Nsxl2vpn Edge under datacenter B click on Action select Power and click on Power on.
(9) check after few minutes the VPN Status by clicking Show L2VPN Statistic.
be sure its up. select PGW01 select VPN under Manage select L2VPN enable and click on publish changes.
Add new Logical Switch: "Application-Tier-01"
NSX Edges -> Perimeter-Gateway-01 -> Manage -> Settings -> Interfaces -> edit vNIC4
Name: Extend-LS-01
Type: Trunk
Connected To:
Distributed Portgroup: vds-mgmt-a_trunknetwork
Add Sub Interface:
L2VPN Settings:
( select VPN under manage and enable L2VPN. click publish changes..
Then below
In actual exam, encryption is = AES256-SHA
(8) go to Vcenter b select datacenter - b. select Nsxl2vpn Edge under datacenter B click on Action select Power and click on Power on.
(9) check after few minutes the VPN Status by clicking Show L2VPN Statistic.
be sure its up. select PGW01 select VPN under Manage select L2VPN enable and click on publish changes.
