Question 1easymultiple choice
Read the full Configure and Manage vSphere Storage explanation →VCP-DCV Configure and Manage vSphere Storage • Complete Question Bank
Complete VCP-DCV Configure and Manage vSphere Storage question bank — all 0 questions with answers and detailed explanations.
Refer to the exhibit. vmkfstools -P -v10 /vmfs/volumes/datastore1/vm1/vm1.vmdk Output: DISKOPEN: /vmfs/devices/disks/naa.6000c29a1b2c3d4e:1: Size 17179869184 (512 bytes sectors) DISKOPEN: /vmfs/devices/disks/naa.6000c29a1b2c3d4e:2: Size 8589934592 (512 bytes sectors) DISKOPEN: /vmfs/devices/disks/naa.6000c29a1b2c3d4e:3: Size 4294967296 (512 bytes sectors) vmfs version: 6.82 capacity: 17179869184 (16.0 GB) format: 3 (vmfs6) number of extents: 3
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.
Virtual Distributed Switch
Virtual Standard Switch
vSphere Installation Bundle
vSphere Storage APIs for Array Integration
vSphere APIs for Storage Awareness
Drag a concept onto its matching description — or click a concept then click the description.
62 TB
256
6 TB
64
1024
esxcli storage core device list
=======================
Device: naa.6000eb3a10e71d0023f04b28b6544000
Device Display Name: DGC Fibre Channel Disk (naa.6000eb3a10e71d0023f04b28b6544000)
Size: 2048.00 GB
Device Type: Direct-Access
Multipath Plugin: NMP
Is Local: false
Is SAS: false
Is USB: false
Is NMP: true
Is PAE: false
Number of Paths: 4
Primary Storage Array Type: VMW_SATP_ALUA
Storage Array Type: VMW_SATP_ALUA
Path Selection Policy: VMW_PSP_FIXED
Path Selection Policy Device Config: {preferred=none}
Console Device: /vmfs/devices/disks/naa.6000eb3a10e71d0023f04b28b6544000vsan.check.health - Cluster Health ----------------------------- - vSAN object health: Degraded - vSAN object repair: In progress - Resyncing objects: 2 - Resyncing data size: 120.00 GB - Active rebalance tasks: 0 - Data efficiency: 1.2x (compression + dedup)
vmkfstools -P -v 10 /vmfs/volumes/datastore1 VMFS version 6.82 Number of extents: 2 Extent 0: /vmfs/devices/disks/naa.6000eb3a10e71d0023f04b28b6544000:1 offset: 0, size: 1048576 (blocks), block size: 1MB Extent 1: /vmfs/devices/disks/naa.6000eb3a10e71d0023f04b28b6544001:1 offset: 0, size: 2097152 (blocks), block size: 1MB
Device: naa.6000c29d123456789
Storage Array Type: VMW_SATP_ALUA
Path Selection Policy: VMW_PSP_RR
Paths:
vmhba3:C0:T0:L0 – state: active
vmhba3:C0:T1:L0 – state: standby{
"policy": {
"hostFailuresToTolerate": 1,
"objectSpaceReservation": 0,
"stripeWidth": 1,
"forceProvisioning": false
}
}2023-01-15T10:30:00.123Z cpu0:12345) NMP: nmp_DeviceStartIo: Device "naa.6000097000019270" failed to issue command due to Not Found (SCSI Sense: H:0x0 D:0x2 P:0x0).
Refer to the exhibit. Output from vmkfstools command: vmkfstools -V /vmfs/volumes/datastore1/vm1/vm1.vmdk Disk descriptor file: /vmfs/volumes/datastore1/vm1/vm1.vmdk # Disk DescriptorFile version=1 CID=12345678 parentCID=ffffffff createType="vmfs" # Extent description RW 1048576000 VMFS "vm1-flat.vmdk" # The Disk Data Base #DDB The VM is using a virtual mode RDM? (Based on the descriptor, is this a virtual RDM?)
Refer to the exhibit.
VASA Storage Capability JSON from an array:
{
"capabilities": [
{
"id": "capacityByThin",
"description": "Thin provisioning",
"properties": {
"provisioningType": {
"type": "string",
"value": "thin"
}
}
},
{
"id": "replication",
"description": "Replication at storage container level",
"properties": {
"rpo": {
"type": "integer",
"value": 3600
}
}
}
]
}Refer to the exhibit. ~ # esxcli storage nmp path list fc.20000010a1234:5006016844e0a6a6-naa.600601607...-fc.20000010a1234:5006016844e0a6a7 State: active (optimized) SATP: VMW_SATP_DEFAULT_AA PSP: VMW_PSP_MRU fc.20000010a1234:5006016844e0a6a7-naa.600601607...-fc.20000010a1234:5006016844e0a6a8 State: active (non-optimized) SATP: VMW_SATP_DEFAULT_AA PSP: VMW_PSP_MRU fc.20000010a1234:5006016844e0a6a8-naa.600601607...-fc.20000010a1234:5006016844e0a6a9 State: active (non-optimized) SATP: VMW_SATP_DEFAULT_AA PSP: VMW_PSP_MRU fc.20000010a1234:5006016844e0a6a9-naa.600601607...-fc.20000010a1234:5006016844e0a6a6 State: active (non-optimized) SATP: VMW_SATP_DEFAULT_AA PSP: VMW_PSP_MRU
vmkfstools -Ph /vmfs/volumes/VSAN-DS VMFS version 3.61 Number of extents: 1 Capacity 2.0 TB (2199023255552 bytes) Free space 123.5 GB (132542701568 bytes) Max file size 2.0 TB (2199023255552 bytes) Max file name length: 255 characters Number of files: 1542 Number of directories: 12 Number of links: 0 Number of VMFS pointer blocks: 0 Number of resource maps: 0
# esxcli storage nfs41 list Volume Name Host Share Accessible Mounted ----------- ----------- -------------- ---------- ------- nfs-ds nas01.local /exports/nfs01 true true # esxcli storage nfs41 param set -v nfs-ds -p MaxQueueDepth -v 64 # esxcli storage nfs41 param list -v nfs-ds Parameter Value ------------------- ----- MaxQueueDepth 64 MaxReadTransferSize 131072 MaxWriteTransferSize 131072 ...
status = 'fail' msg = 'Failed to enable vSAN on host 192.168.1.100: vSAN requires at least one disk group with a capacity tier.' host = '192.168.1.100'
Storage DRS Configuration for Datastore Cluster 'DS-Cluster':
Automation Level: Manual
Runtime Settings:
Invocation Frequency: 8 hours
Threshold: Utilization 80% (Conservative)
I/O Metrics: Enabled
I/O Latency Threshold: 15 ms
Power Management: Disabled
Advanced Options:
minSpaceUtilizationDiff: 50 GB
minIOLatencyDiff: 5 msError: Cannot add host 'esxi-05.lab.local' to vSAN cluster. Cause: Host esxi-05.lab.local does not have a VMkernel interface with vSAN traffic enabled. VMkernel interfaces on host: vmk0: Management (10.0.0.5) vmk1: vMotion (10.0.1.5) vmk2: Provisioning (10.0.2.5)