Deployment Guide
Table Of Contents
- Dell EMC PowerVault ME4 Series Storage System Deployment Guide
- Contents
- Before you begin
- Mount the enclosures in the rack
- Connect to the management network
- Cable host servers to the storage system
- Cabling considerations
- Connecting the enclosure to hosts
- Host connection
- Connect power cables and power on the storage system
- Perform system and storage setup
- Record storage system information
- Using guided setup
- Web browser requirements and setup
- Access the PowerVault Manager
- Update firmware
- Use guided setup in the PowerVault Manager Welcome panel
- Perform host setup
- Host system requirements
- Windows hosts
- Configuring a Windows host with FC HBAs
- Configuring a Windows host with iSCSI network adapters
- Configuring a Windows host with SAS HBAs
- Linux hosts
- Configuring a Linux host with FC HBAs
- Configure a Linux host with iSCSI network adapters
- Attach a Linux host with iSCSI network adapters to the storage system
- Assign IP addresses for each network adapter connecting to the iSCSI network
- Register the Linux host with iSCSI network adapters and create volumes
- Enable and configure DM Multipath on the Linux host with iSCSI network adapters
- Create a Linux file system on the volumes
- SAS host server configuration for Linux
- VMware ESXi hosts
- Fibre Channel host server configuration for VMware ESXi
- iSCSI host server configuration for VMware ESXi
- Attach an ESXi host with network adapters to the storage system
- Configure the VMware ESXi VMkernel
- Configure the software iSCSI adapter on the ESXi host
- Register an ESXi host with a configured software iSCSI adapter and create and map volumes
- Enable multipathing on an ESXi host with iSCSI volumes
- Volume rescan and datastore creation for an ESXi hosts with iSCSI network adapters
- SAS host server configuration for VMware ESXi
- Citrix XenServer hosts
- Fibre Channel host server configuration for Citrix XenServer
- iSCSI host server configuration for Citrix XenServer
- Attach a XenServer host with network adapters to the storage system
- Configure a software iSCSI adapter on a XenServer host
- Configure the iSCSI IQN on a XenServer host
- Enable Multipathing on a XenServer host
- Register a XenServer host with a software iSCSI adapter and create volumes
- Create a Storage Repository for a volume on a XenServer host with a software iSCSI adapter
- SAS host server configuration for Citrix XenServer
- Troubleshooting and problem solving
- Locate the service tag
- Operators (Ops) panel LEDs
- Initial start-up problems
- Cabling for replication
- SFP+ transceiver for FC/iSCSI ports
- System Information Worksheet
- Setting network port IP addresses using the CLI port and serial cable
Use the PowerVault Manager to verify any faults found while viewing the LEDs. If the LEDs cannot be viewed due to the
location of the system, use the PowerVault Manager to determine where the fault is occurring . This web-application provides
you with a visual representation of the system and where the fault is occurring. The PowerVault Manager also provides more
detailed information about CRUs, data, and faults.
Review the event logs
The event logs record all system events. Each event has a numeric code that identifies the type of event that occurred, and has
one of the following severities:
● Critical – A failure occurred that may cause a controller to shut down. Correct the problem immediately.
● Error – A failure occurred that may affect data integrity or system stability. Correct the problem as soon as possible.
● Warning – A problem occurred that may affect system stability, but not data integrity. Evaluate the problem and correct it if
necessary.
● Informational – A configuration or state change occurred, or a problem occurred that the system corrected. No immediate
action is required.
The event logs record all system events. Review the logs to identify fault and cause of the failure. For example, a host could lose
connectivity to a disk group if a user changes channel settings without taking the storage resources that are assigned to it into
consideration. In addition, the type of fault can help you isolate the problem to either hardware or software.
Isolate the fault
Occasionally, it might become necessary to isolate a fault. This is true with data paths, due to the number of components
comprising the data path. For example, if a host-side data error occurs, it could be caused by any of the components in the data
path: controller module, cable, or data host.
If the enclosure does not initialize
It may take up to two minutes for all enclosures to initialize.
If an enclosure does not initialize:
● Perform a rescan
● Power cycle the system
● Make sure that the power cord is properly connected, and check the power source to which it is connected
● Check the event log for errors
Correcting enclosure IDs
When installing a system with expansion enclosures attached, the enclosure IDs might not agree with the physical cabling order.
This issue occurs if the controller was previously attached to enclosures in a different configuration, and the controller attempts
to preserve the previous enclosure IDs.
To correct this condition, ensure that both controllers are up, and perform a rescan using the PowerVault Manager or the CLI.
The rescan reorders the enclosures, but it can take up to two minutes to correct the enclosure IDs.
NOTE:
Reordering expansion enclosure IDs only applies to dual-controller mode. If only one controller is available, due to a
controller failure, a manual rescan does not reorder the expansion enclosure IDs.
● To perform a rescan using the PowerVault Manager:
1. Verify that both controllers are operating normally.
2. In the System tab, click Action, and select Rescan Disk Channels.
● To perform a rescan using the CLI, type the following command:
rescan
Troubleshooting and problem solving
85