300-610 · Question #223
Refer to the exhibit. A Cisco engineer is configuring a next-generation Cisco HyperFlex HX data platform with 2 x Cisco UCS 6248UP fabric interconnects, 8 x Cisco HX-Series HX240c-M4SX servers, plus 8
The correct answer is B. The servers have duplicate names. The most probable reason for some HyperFlex HX Native snapshots failing to create is that the virtual machines have duplicate names within the environment.
Question
Refer to the exhibit. A Cisco engineer is configuring a next-generation Cisco HyperFlex HX data platform with 2 x Cisco UCS 6248UP fabric interconnects, 8 x Cisco HX-Series HX240c-M4SX servers, plus 8 x Cisco UCS B200-M4 blade servers, Cisco UCS 5108 blade chassis, and Cisco UCS 2204XP fabric extenders. The solution is configured with HX Release 4.5(2a) using VMware ESXi 7.0 U2. After the engineer migrates all customer VMs to the new solution platform, the engineer decides to create HX Native snapshots for all the VMs. The engineer performs the operation and notices that some of the VMs are not creating snapshots. What is the most probable reason that the HX Native snapshots are not created?
Exhibit
Options
- AVirtual machines are in suspended state
- BThe servers have duplicate names
- CThe source disk is thick provisioned
- DThe node has insufficient datastore space
How the community answered
(26 responses)- A4% (1)
- B77% (20)
- C8% (2)
- D12% (3)
Why each option
The most probable reason for some HyperFlex HX Native snapshots failing to create is that the virtual machines have duplicate names within the environment.
Virtual machines in a suspended state are typically paused and can often still be snapshotted, though it might not be a consistent snapshot.
Cisco HyperFlex HX Native snapshots rely on unique identification of virtual machines. If there are virtual machines with duplicate names within the vCenter inventory or the HyperFlex environment, it can cause conflicts or prevent the HX system from correctly identifying and managing the snapshot operations for those specific VMs, leading to snapshot failures.
The source disk being thick provisioned generally does not prevent snapshots from being created; HyperFlex supports both thick and thin provisioned disks for VMs.
Insufficient datastore space could prevent snapshots, but duplicate server/VM names are a more specific and common cause for *some* VMs failing while others succeed, especially in migrated environments.
Concept tested: Cisco HyperFlex HX Native snapshots troubleshooting
Source: https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/hx/hx_data_platform_software/4_5/quick_start/b_hx_45_quick_start_guide.html
Topics
Community Discussion
No community discussion yet for this question.