Which three components are required in an MX7000 chassis to allow multiple compute sleds to share access to the same disks in an MX5016s enclosure? (Select 3)

Question

Options

• APERC H745PMX
• BDrive-assigned storage configuration
• CMX5000s IOM
• DCluster-aware Operating System
• EHBA 330MMZ

• A
  31% (11)
• B
  51% (18)
• C
  17% (6)

Explanation

Sharing storage across compute sleds in an MX7000 requires three cooperating layers: a drive-assigned storage configuration (B) maps specific MX5016s drives to the appropriate compute sleds at the fabric level; an HBA 330MMZ (E) provides pass-through SAS connectivity without taking exclusive RAID ownership of the drives; and a cluster-aware OS (D) coordinates simultaneous multi-node disk access to prevent data corruption.

Why A (PERC H745PMX) is wrong: A PERC card is a RAID controller - it claims exclusive ownership of attached drives and presents them as RAID volumes, making shared access by multiple hosts impossible. Shared storage requires a pass-through HBA (the HBA 330MMZ), not a RAID controller.

Why C (MX5000s IOM) is wrong: The MX5000s is a network I/O module for fabric/switching connectivity within the chassis, not a component that enables shared storage access to the MX5016s enclosure.

Memory tip: Think "Config → Connector → Coordinator" - you need the storage Configuration (B) to assign drives, the right Connector (E, an HBA not a RAID card) to pass through access, and an OS Coordinator (D) to safely arbitrate multi-node writes. If any one of these three is missing, shared disk access either fails or corrupts data.

No community discussion yet for this question.