一番質高い 3V0-643 試験問題集

You have been tasked with modifying an existing NSX API call to capture flow information for an organization. The existing API call is located on the ControlCenter desktop in a file name flowapi.txt.
The API call should be modified to collect Layer3 flow statistics between the dev-web-01a and the ControlCenter virtual machine.
Requirements:
vCenter: vcsa01a.corp.local
Credential: [email protected] / VMware1!
File location: flowapi.txt on the desktop of ControlCenter.
Modify and Save the existing API call to capture the requested information.
A REST Client has been added to Chrome and Firefox for this exercise.
Output the Response Body to a text file called apiresults.txt on the desktop of ControlCenter.
******************flowapi.txt***********************
https://<nsxmgr-ip>/api/2.1/app/flow/flowstats?contextId=datacenter-21&flowType=TCP_UDP&startTime
=0&endTime=
https://192.168.110.15/api/2.1/app/flow/flowstats?contextId=vm-26&flowType=Layer3&startTime=0&endT ime=1320917094000&
******************flowapi.txt***********************
HOL LAB for Practice:
See the explanation part for complete solution.

SOLUTION:
Access the MOB by entering the following URL
https://vcsa-01a.corp.local/mob
[email protected]
VMware1!




Note down the vm number of dev-web-01a (in exam its like vm-216)
Then update flowapi.txt as
******************flowapi.txt***********************
https://<nsxmgr-ip>/api/2.1/app/flow/flowstats?contextId=datacenter-21&flowType=TCP_UDP&startTime
=0&endTime=
https://192.168.110.15/api/2.1/app/flow/flowstats?contextId=vm-216&flowType=Layer3
&startTime=0&endTime=1320917094000&startIndex=0&pageSize=2
******************flowapi.txt***********************
Then go to RESTClient.
GET
https://192.168.110.15/api/2.1/app/flow/flowstats?contextId=vm-216&flowType=Layer3
&startTime=0&endTime=1320917094000&startIndex=0&pageSize=2
SEND
Copy the content of "Response Body"
Paste in notepad and Save As "apiresults.txt"on the desktop of ControlCenter.

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.

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.

Enable load balancing for the development environment allowing HTTPS access to the Dev-Web-01a and Dev-Web-02a servers.
Requirements:
vCenter: vcsa-01a.corp.local
Credentials: [email protected]
Self-signed certificate parameters:
Common Name: 192.168.5.100
Organization Name: ABC Medical
Organization Unit: IT
Locality: Palo Alto
State: CA
Country: United States
Message Algorithm: RSA
Key Size: 2048
Number of Days: 365
Web Servers: Dev-Web-01a, Dev-Web-02a
Use the secondary IP address of 192.168.5.100
New connections should consider current connections among all available members of the pool.
The web servers will not have SSL certificates installed. The web team has indicated that analytics based on source IP should be available.
Ensure all requirements have been met.
HOL LAB for Practice:
Load Balancer and other questions 7, 8, 9
See the explanation part for complete solution.

SOLUTION:
Create Secondary address on Uplink Interface.
Generate CSR using the give details.
Enable Load-Balancer, create Profile, create Virtual Server.
Dev-Edge -> Manage -> Settings -> Interfaces -> Edit and add secondary IP address: 192.168.5.100




Create CSR as per given details from the question:
Dev-Edge -> Manage -> Settings -> Certificate -> Actions -> Generate CSR


Dev-Edge -> Manage -> Settings -> Certificate -> Actions -> Self Sign Certificate: Days = 365



Dev-Edge -> Manage -> Load Balancer -> Global Configuration -> Edit

Enable Load Balancer

Create Application Profile:

Check box for inser-forward-for-httpheader also below

Create new Pool:


Add both Web member servers:








Add Virtual Servers: