VCP-DCV Configure and Manage vSphere Networking • Complete Question Bank
Complete VCP-DCV Configure and Manage vSphere Networking question bank — all 0 questions with answers and detailed explanations.
Drag a concept onto its matching description — or click a concept then click the description.
Basic virtualization with vMotion and HA
Full features including DRS, DPM, and Host Profiles
Includes performance monitoring and capacity management
Adds AppDefense for security
Licensing for small ROBO deployments
Refer to the exhibit. # esxcli network ip connection list | grep -E "10.10.10.1|10.10.10.2" tcp 0 0 10.10.10.1:22 10.10.10.2:45678 ESTABLISHED new-session udp 0 0 10.10.10.1:123 0.0.0.0:* # esxcli network ip route ipv4 list Network Netmask Gateway Interface 0.0.0.0 0.0.0.0 10.10.10.254 vmk0 10.10.10.0 255.255.255.0 0.0.0.0 vmk0 169.254.0.0 255.255.0.0 0.0.0.0 vmk1
Refer to the exhibit.
<config>
<vswitch name="vSwitch0">
<portgroup name="VM Network">
<vlan>0</vlan>
<nicteaming>
<policy>
<failover>yes</failover>
<loadbalance>srcmac</loadbalance>
<active>vmnic0,vmnic1</active>
</policy>
</nicteaming>
</portgroup>
</vswitch>
</config>A company runs a three-tier application on vSphere 7.0. The web tier uses VLAN 100, app tier VLAN 200, and database tier VLAN 300. Each tier is on a separate port group on a vSphere distributed switch. The environment uses Network I/O Control (NIOC) with shares set to: Web (50), App (30), Database (20). The physical uplinks are two 10 GbE NICs in a team. Recently, the database team reports slow performance during peak hours. The network team checks the physical switches and finds no congestion. The ESXi host shows the two uplinks are heavily utilized with many dropped packets on the database port group. The administrator suspects that the database traffic is being starved by other traffic. Which action should the administrator take to resolve the issue?
A. Increase the number of physical uplinks to four 10 GbE NICs. B. Change the NIOC shares to Web (10), App (30), Database (60). C. Create a separate vSphere standard switch for the database tier. D. Enable SR-IOV on the physical NICs and assign virtual functions to database VMs.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag steps to the numbered slots on the right, or tap a step then tap a slot.
Drag a concept onto its matching description — or click a concept then click the description.
Distributes VM workloads across hosts based on resource usage
Provides continuous availability by maintaining a secondary VM
Migrates VM storage without downtime
Powers hosts on/off to save energy based on demand
Standardizes host configuration across a cluster
~ # esxcli network vswitch dvs health list -n vds1 Uplink0: healthy Uplink1: healthy VLAN 100: health unknown due to missing VMkernel adapter
~ # esxcli network vswitch dvs vmware lag list -n vds1 LAG ID Name Uplinks Mode Load Balancing 0 LAG0 vmnic0,vmnic1 passive Source and Destination IP
~ # esxcli network vswitch dvs networkresourcepool list -n vds1 Name: Management Shares: 50 Reservation: 0 Limit: -1 (unlimited) Name: vMotion Shares: 50 Reservation: 500 Limit: -1 (unlimited) Name: NFS Shares: 100 Reservation: 0 Limit: -1 (unlimited)
Refer to the exhibit. ``` esxcli network ip interface list vmk0 Name: vmk0 MAC Address: 00:50:56:60:00:01 Enabled: true Portset: vSwitch0 Portgroup: Management Network VDS Name: N/A IP Address: 192.168.1.10 Subnet Mask: 255.255.255.0 MTU: 1500 vmk1 Name: vmk1 MAC Address: 00:50:56:60:00:02 Enabled: true Portset: dvs1 Portgroup: iSCSI Network VDS Name: dvs1 IP Address: 192.168.20.10 Subnet Mask: 255.255.255.0 MTU: 9000 ```
Refer to the exhibit.
```
Net-DVS: Up
Error: None
DVS Name: dvs0
DVS Port: 1
Uplink: no
Host: esxi01.example.com
MAC Addr: 00:50:56:60:00:0a
Healthcheck:
VLAN ID: 100
MTU: 1500
VLAN Status: OK
MTU Status: OK
Teaming:
Policy: Route based on originating virtual port
Active Uplinks: vmnic0, vmnic1
Standby Uplinks: none
Load Balancing: Disabled
```Refer to the exhibit.
[root@esxi01:~] esxcli network vswitch standard list
Standard Switch: vSwitch0
Name: vSwitch0
Class: cSwitch
Num Ports: 128
Used Ports: 3
Configured Ports: 128
MTU: 1500
CDP: listen
Beacon Enabled: false
Beacon Interval: 0
Uplinks: vmnic0
Portgroups:
Management Network
VLAN ID: 0
Used Ports: 1
Uplinks: vmnic0
VM Network
VLAN ID: 100
Used Ports: 1
Uplinks: vmnic0
VMkernel Network Adapters:
vmk0
Portgroup: Management Network
IP Address: 192.168.1.10
Subnet Mask: 255.255.255.0
MAC Address: 00:50:56:ab:01:01esxcli network ip connection list | grep -E "443|80" tcp 0 0 192.168.100.10:443 192.168.100.20:54321 ESTABLISHED new-socket tcp 0 0 192.168.100.10:80 192.168.100.30:12345 TIME_WAIT new-socket tcp 0 0 ::ffff:192.168.100.10:443 ::ffff:192.168.100.40:65432 ESTABLISHED new-socket netstat -an | grep -E "443|80" tcp 0 0 192.168.100.10:443 0.0.0.0:* LISTEN tcp 0 0 192.168.100.10:80 0.0.0.0:* LISTEN tcp6 0 0 :::443 :::* LISTEN
esxcli network vswitch standard list
VSwitchName: vSwitch0
Portgroup Name: Management Network
VLAN ID: 0
Active uplinks: vmnic0
Standby uplinks: vmnic1
Portgroup Name: VM Network
VLAN ID: 100
Active uplinks: vmnic0
Standby uplinks: vmnic1
VSwitchName: vSwitch1
Portgroup Name: Storage Network
VLAN ID: 200
Active uplinks: vmnic2
Standby uplinks: vmnic3esxcli network ip interface ipv4 get Name IPv4 Address IPv4 Netmask IPv4 Broadcast Address Type DHCP DNS vmk0 192.168.10.10 255.255.255.0 192.168.10.255 STATIC false vmk1 10.0.0.10 255.255.255.0 10.0.0.255 STATIC false vmk2 172.16.0.10 255.255.255.0 172.16.0.255 STATIC false esxcli network ip route ipv4 list Network Netmask Gateway Interface 192.168.10.0 255.255.255.0 0.0.0.0 vmk0 default 0.0.0.0 192.168.10.1 vmk0 10.0.0.0 255.255.255.0 0.0.0.0 vmk1 172.16.0.0 255.255.255.0 0.0.0.0 vmk2
esxcli network ip dns server list DNSServers: 192.168.10.2, 192.168.10.3 esxcli network ip dns search list SearchDomains: localdomain esxcli network ip dns suffix list Suffixes: localdomain vmkping -c 3 192.168.10.2 PING 192.168.10.2 (192.168.10.2): 56 data bytes 64 bytes from 192.168.10.2: icmp_seq=0 ttl=128 time=0.456 ms 64 bytes from 192.168.10.2: icmp_seq=1 ttl=128 time=0.512 ms 64 bytes from 192.168.10.2: icmp_seq=2 ttl=128 time=0.478 ms vmkping -c 3 hostname.localdomain ping: unknown host hostname.localdomain
esxcli network vswitch dvs vmware list VDS Name: VDS-01 Uplink ports: 4 Number of portgroups: 5 MTU: 1500 LACP: Enabled (Active) NetFlow: Enabled (collector 192.168.100.50:2055) Health check: Enabled esxcli network vswitch dvs vmware uplink list Uplink Port Uplink Name Physical NIC Link Status 0 uplink0 vmnic0 Up 1 uplink1 vmnic1 Up 2 uplink2 vmnic2 Down 3 uplink3 vmnic3 Down
esxcfg-vswitch -l Switch Name Num Ports Used Ports Configured Ports MTU Uplinks vSwitch0 128 5 128 1500 vmnic0 VLAN ID: 0 DVS Name Num Ports Used Ports Configured Ports MTU Uplinks DSwitch 256 12 256 9000 vmnic1, vmnic2 DVPortgroup: Management (VLAN 100, ports: 3) DVPortgroup: Production (VLAN 200, ports: 5) DVPortgroup: Storage (VLAN 300, ports: 4) vmkping -I vmk0 192.168.100.1 PING 192.168.100.1 (192.168.100.1): 56 data bytes 64 bytes from 192.168.100.1: icmp_seq=0 ttl=64 time=0.345 ms --- 192.168.100.1 ping statistics --- 1 packets transmitted, 1 packets received, 0% packet loss
net-dvs -l | grep -A 20 "DVS name: DSwitch"
DVS name: DSwitch
vcenter: vcenter.lab.local
uuid: 50 1a 2b 3c 4d 5e 6f 70 80 90 a0 b0 c0 d0 e0 f0
numPorts: 256
switchType: distributed
version: 7.0.0
uplinkPorts: 4
host: esxi1.lab.local (vmnic1, vmnic2)
host: esxi2.lab.local (vmnic1, vmnic2)
host: esxi3.lab.local (vmnic1, vmnic2)
host: esxi4.lab.local (vmnic1, vmnic2)
Port group: Production
VLAN: 200
Used by: VM1, VM2, VM3
Active uplinks: vmnic1, vmnic2
Standby uplinks: (none)
Load balancing: Route based on IP hash
Network failure detection: Beacon probing onlyvsish -e get /net/portsets/DvsPortset-0/ports/200/status Port 200 Status: Link up: yes Speed (Mbps): 10000 Duplex: full MTU: 1500 Packets received: 1024 Packets transmitted: 2048 Errors: 0 Drops: 0 vsish -e get /net/portsets/DvsPortset-0/ports/200/filter Filtering: Allowed MAC addresses: (none) Allowed VLANs: 100, 200, 300 Blocked VLANs: (none) net-stats -l | grep "DvsPortset-0:200" DvsPortset-0:200 TX packets:2048 RX packets:1024 TX errors:0 RX errors:0 TX drops:0 RX drops:0
esxcli network ip dns server list
DNSServers: 10.0.0.1, 10.0.0.2
esxcli network ip interface list
vmk0: IP: 192.168.10.10/24 MAC: 00:50:56:ab:cd:01 MTU: 1500
vmk1: IP: 192.168.20.10/24 MAC: 00:50:56:ab:cd:02 MTU: 1500
Default gateway: 192.168.20.1
esxcli network ip route ipv4 list
Network Netmask Gateway Interface
0.0.0.0 0.0.0.0 192.168.20.1 vmk1
192.168.10.0 255.255.255.0 0.0.0.0 vmk0
192.168.20.0 255.255.255.0 0.0.0.0 vmk1
vmkping -I vmk0 10.0.0.1
Ping using interface vmk0 (192.168.10.10/24):
Connect to host 10.0.0.1: Network is unreachableethtool -S vmnic0 | grep -E "(rx_errors|tx_errors|rx_dropped|tx_dropped)"
rx_errors: 0
tx_errors: 0
rx_dropped: 120
tx_dropped: 0
netstat -i | grep vmnic0
Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll
vmnic0 1500 192.168.1.0 192.168.1.10 5000 0 6000 0 0
vsish -e get /net/portsets/vSwitch0/ports/1/status
Link up: yes
Packets received: 5000
Packets transmitted: 6000
Receive errors: 0
Transmit errors: 0
Receive drops: 0
Transmit drops: 0
vmkping -I vmk0 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=0.234 ms
--- 192.168.1.1 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss