Md3000 Maintenance Considerations - Dell PowerVault MD3000 Information Update

Dell powervault md3000: user guide
Hide thumbs Also See for PowerVault MD3000:
Table of Contents

Advertisement

Available languages
  • EN

Available languages

  • ENGLISH, page 1
MD3000 Configuration Considerations
When configuring the MD3000, consider the following updates.
SAS Connections
OpenManage™ software users who want to install a SAS 5/E connected to an MD3000 storage array
must first download and install the OM5.1.0.1 patch from the Dell Support website at support.dell.com.
This is a prerequisite in order for the OpenManage software to function properly.
Cluster Configuration Considerations for Standalone Host Servers
If one of the standalone host servers you are planning to configure into a cluster environment is running
MD Storage Manager and has a virtual disk mapped to the array, use that host to create the Host Group
and quorum virtual disk mapping.
NOTE:
Failure to follow this mapping protocol can cause the host server to lose communication with the array if
the server is using only in-band management and only one of the servers has a virtual disk mapped to the array. If
communication is lost, restore in-band management to the other host server and complete the cluster setup using
the following steps:
1 Using MD Storage Manager from either the host server with restored in-band management or
from a management station, click Configure→ Create Host-to-Virtual Disk Mappings.
2 Select the host server name that does not have a virtual disk mapped.
3 Click Access to access the virtual disk.
4 Assign a logical unit number (LUN) of 31.
5 Click Finish.

MD3000 Maintenance Considerations

For Linux kernels, stop and then restart the SMagent after performing either of the two following
maintenance tasks:
Moving a controller offline or replacing a controller.
Removing SAS cables from or attaching SAS cables to Red Hat Enterprise Linux (version 4),
SUSE Linux Enterprise Server 9, or SUSE Linux Enterprise Server 10 host servers.
NOTE:
If a Resolve Topology Conflicts message appears in the Status portlet of the Summary page after restarting
the SMagent, it might be necessary to restart the host server to clear this message. The Resolve selection in the
Topology Conflict wizard should not be selected. The MD3000 will continue to service I/O requests; however, the
array could become partially managed if only in-band management is used. Stop all I/O operations on any host
servers that were involved in the maintenance operation and perform a restart.
4
Information Update

Advertisement

Table of Contents
loading

Table of Contents