Dell PowerVault MD3000 - Manual (Page 2)

2
׀
Dell PowerVault Data MD3000 Support Matrix
Rule First
Gen.
Second
Gen.
The management Ethernet part of the RAID controller
module must be connected to a switch port that is
configured to use Auto-Negotiate √ √
Connecting an MD3000 and MD3000i to the same host is
supported. √
Up to two MD1000 expansion enclosures can be attached
to the MD3000 for a total of 45 SAS and/or SATA physical
disks. √ √
Attached MD1000 expansion enclosures must be run in
unified mode. √ √
The enclosure can contain a mixture of SAS and SATA II
physical disks. √ √
Do not mix SAS and SATA disks in a disk group. √ √
A hot spare for a disk group must be a physical disk of equal
or greater size than any of the member disks. √ √
The hot spare for a disk group with SAS physical disks must
be a SAS disk. √ √
The hot spare for a disk group with SATA physical disks
must be a SATA disk. √ √
When using out-of-band management with SMcli by
specifying the RAID Controller management port IP
addresses on the MD Storage Array, SMcli commands that
change the attributes of a virtual disk, virtual disk copy, or
snapshot virtual disk, must have management access to the
owning RAID Controller Module to complete. Where
applicable it is a best practice to specify both management
port IP addresses on the SMcli invocation: "SMcli
192.168.128.101 192.168.128.102 -c". √ √
Only the Dell Linux MPP multi-path driver should be
loaded on a Linux host server*** √ √
MD3000 and MD3200 series supported on a single Linux
host.*** √
Dell MPP drivers are required for multi-path support (refer
to Table 8). Linux open framework dm-mpp (multi-path)
drivers are not supported with the MD3000. √ √
Virtual disks on an MD3000 cannot be used for booting. √ √
Maximum Virtual Disk Size cannot exceed 2 Terabytes. √
Each virtual disk is limited to a maximum of 30 physical √