Release Notes P/N Rev A07

(1)

These release notes contain information about features, system requirements, and limitations in PowerPath Version 5.6 and its minor releases for Linux.

◆ Revision history ... 2

◆ Product description... 3

◆ New features and changes ... 4

◆ Fixed problems ... 8

◆ Environment and system requirements... 8

◆ Known problems and limitations ... 17

◆ Technical notes... 25

◆ Documentation ... 35

◆ Software media, organization, and files... 38

◆ Installation ... 39

◆ Troubleshooting and getting help... 41 Version 5.6 and Minor Releases

Release Notes

P/N 300-011-782 Rev A07 March 07, 2012

(2)

Revision history

The following table presents the revision history of this document.

Revision Date Description

A01 April 4, 2011 First release of this document for PowerPath 5.6 for Linux.

A02 June 13, 2011 Updated the“New features and changes”section with the following:

• PowerPath Viewer support information • VPLEX 5.0 support information

A03 September 30, 2011 Updated for PowerPath 5.6 P01 on Oracle Linux and Oracle VM 3.0 Server.

• Updated the“New features and changes”section onpage 4.

• Updated the“Support changes”section onpage 7. • Updated the“Support Summary”section on

page 10.

• Updated the“Supported Linux distributions”section onpage 13.

• Added the“PowerPath and VMAX/VMAXe series devices”section onpage 26.

A04 November 16, 2011 Depreciation announcement of support for Linux 32-bit operating systems. See“Support changes” on page 7.

A05 December 16, 2011 Release of Linux 5.6 P02. See“PowerPath 5.6 P02” on page 5.

A06 December 28, 2011 Updated the“Support Summary”table onpage 10

with VPLEX and Geosynchrony support.

(3)

Product description

The EMC®PowerPath®family of products includes:

◆ _{PowerPath multipathing software for physical environments, as}

described in“PowerPath multipathing” on page 3.

◆ _{PowerPath Migration Enabler}®_{, as described in}_“PowerPath Migration Enabler” on page 3.

◆ _{PowerPath Encryption with RSA}®_{, as described in}_“PowerPath Encryption with RSA” on page 4.

Your license type determines the extent PowerPath functionality is available. PowerPath Migration Enabler for Encapsulation, Host Copy, Open Replicator, and TimeFinder/Clone®require a separate license key. PowerPath Encryption with RSA requires a separate license key. If you have questions about your license, contact your EMC Customer Support Representative.

PowerPath multipathing

PowerPath is a server-resident software solution designed to enhance performance and application availability. PowerPath combines automatic load balancing, path failover, and multiple path I/O capabilities into one integrated package.

PowerPath enhances application availability by providing load balancing and automatic path failover and recovery functionality. PowerPath supports servers, including cluster servers, connected to EMC and third-party arrays.

PowerPath Migration Enabler

EMC PowerPath Migration Enabler is a host-based migration tool that allows you to migrate data between storage systems, or in the case of EMC TimeFinder/Clone, between devices within an EMC Symmetrix®storage system. PowerPath Migration Enabler uses the PowerPath filter driver, in conjunction with an underlying

technology, to provide nondisruptive or minimally disruptive data migrations.

(4)

The underlying technologies for Migration Enabler are EMC Encapsulation, EMC Open Replicator for Symmetrix, EMC Host Copy (host-based copy), and EMC TimeFinder/Clone. Migrations can be non-disruptive when pseudo device names are used. When native names are used, a minor disruption may be necessary to reconfigure the applications to use the target native name. PowerPath Migration Enabler works independently of PowerPath multipathing. However, PowerPath must be installed. The EMC PowerPath

Migration Enabler User Guide provides additional information.

PowerPath Encryption with RSA

PowerPath Encryption with RSA is host-based software distributed with the PowerPath package and requiring a separate product license. PowerPath Encryption provides the following security benefits:

◆ Ensures the confidentiality of data on a disk drive that is

physically removed from a data center.

◆ _{Prevents anyone who gains unauthorized access to the disk from}

reading or using the data on that device.

PowerPath Encryption uses strong encryption protocols to safeguard sensitive data on disk devices. It transparently encrypts data written to a disk device and decrypts data read from it. The EMC PowerPath Encryption with RSA User Guide provides additional information. RSA Key Manager The RSA Key Manager provides key management and automatic

provisioning of encryption keys for PowerPath hosts. The RSA Key Manager consists of two main elements: a central RKM appliance and distributed key manager clients (integrated into the PowerPath host). The RSA Key Manager Appliance Operations Guide provides additional information on the RKM appliance.

New features and changes

This section describes new features and changes by product, as follows:

◆ _{“License ordering and activation” on page 5} ◆ _{“PowerPath multipathing” on page 5} ◆ _{“PowerPath Migration Enabler” on page 7}

(5)

◆ “PowerPath Encryption with RSA” on page 7 ◆ _{“Support changes” on page 7}

Note:Earlier versions of PowerPath for Linux may be qualified with the product versions listed in this section. The E-Lab Interoperability Navigator™provides complete, up-to-date qualification information.

License ordering and activation

Effective February 15, 2011, instead of the physical Right To Use (RTU), the default delivery method for PowerPath licenses is

electronic. An electronic License Authorization Code (LAC) is sent by email in order to redeem the license key on the Powerlink Licensing portal. This does not affect upgrades because PowerPath retains existing license information.

Physical RTU cards are still available as an option. EMC Global Support, at 1-800-svc4emc or 1-800-782-4362, can provide more information. The EMC PowerPath Family Electronic License Ordering Process Technical Notes, available on Powerlink, provides more information about the PowerPath license electronic ordering process.

PowerPath 5.6 P02 PowerPath 5.6 P02 is released to support Oracle Linux 5.x UEK kernel on x86_64 only. Other Linux platforms are not supported.

PowerPath 5.6 P02 is a full-package installation.

◆ _{Boot from SAN support is not available on Oracle Linux 5.x}

running UEK kernel.

PowerPath 5.6 P01 PowerPath 5.6 P01 is released to support only Oracle Linux with UEK kernels on x86_64. Other Linux platforms are not supported.

PowerPath 5.6 P01 is a full-package installation that includes support for the following features:

(6)

Note:Before installing PowerPath 5.6 P01 on a host, ensure that

dm-multipath is disabled on the host. Otherwise, system instability could occur. EMC recommends that you blacklist all non-local devices on a host on which PowerPath will be installed; this action enables multipathing on those default devices.

◆ _{Support for Boot from SAN on Oracle Linux 6.0 and 6.1.}

The Boot from SAN support is not available on Oracle Linux 5.x running UEK kernel.

PowerPath 5.6 PowerPath 5.6 is released to support only the Red Hat, Asianux, and Oracle Linux platforms. Other Linux platforms such as SUSE are not supported.

PowerPath has the following new features:

◆ Support for EMC Symmetrix VMAXe™ arrays with Enginuity™

version 5875.198.148.e.

◆ _{Support for VNX™ Operating Environment (OE) arrays series}

models

◆ Support for VNXe™ Operating Environment (OE) arrays series

models

◆ _{Support for RHEL 6.0 (x86, x86_64), and RHEL 5.6 (x86, x86_64)} ◆ Support for Symmetrix Enginuity 5875 support

◆ _{Support for Invista 2.4 SP1}

◆ Support for HP StorageWorks Enterprise Virtual Array 8400 ◆ _{Support for Open-FCoE initiator in RHEL 6.0}

Note:The Boot from SAN option is an exception for the Open-FCoE feature support.

◆ _{Cluster support:}

• Support for Veritas Cluster Server 5.1, 5.1 SP1, 5.1 SP1 PR2 • Support for Veritas Storage Foundation 5.1 SP1

◆ Support for VPLEX 5.0 with GeoSynchrony 5.0 ◆ _{Support for PowerPath Viewer.}

Note:PowerPath Viewer supports only RHEL and SLES. Therefore, it is not available on PowerPath 5.6 P01, which supports only Oracle Linux platforms.

(7)

PowerPath 5.6 P02 ◆ Support for Oracle Linux 5.7 UEK kernel on x86_64 only PowerPath 5.6 P01 ◆ Support for Oracle Linux 5.6, 6.0, and 6.1 UEK kernels

PowerPath 5.6 ◆ Support for RHEL 6.0 (x86, x86_64), and RHEL 5.6 (x86, x86_64)

PowerPath 5.6 P02 PowerPath Encryption with RSA is not supported.

PowerPath 5.6 P01 PowerPath Encryption with RSA is not supported.

PowerPath 5.6 PowerPath Encryption with RSA has the following new features:

◆ Support for RHEL 5.6 (x86_64) and RHEL 6.0 (x86_64)

Support changes

This section includes changed behavior, end-of-life announcements, and other support changes.

◆ Operating System support: PowerPath 5.6 P01 supports Oracle

Linux (UEK kernels only). It does not support Red Hat compliant kernels in Oracle Linux 5.6, 6.0, and 6.1.

Deprecations

◆ PowerPath 5.6 and minor releases is the last version of PowerPath

for Linux to include qualified support for 32-bit operating systems, and subsequent PowerPath for Linux releases will not support it. Earlier PowerPath for Linux versions will continue to support 32-bit operating systems.

◆ _{PowerPath 5.5 is the last version to support IA64 and PPC64.}

Earlier PowerPath for Linux versions will continue to support them.

◆ PowerPath 5.5 is the last version to support Veritas Storage

Foundation 4.1. Earlier PowerPath for Linux version will continue to support it.

(8)

Fixed problems

This section lists fixed problems by product, as follows:

◆ _{“PowerPath multipathing” on page 8} PowerPath

multipathing

Table 1 on page 8shows fixed problems in PowerPath multipathing.

Environment and system requirements

This section lists interoperability and host configuration information not found in other sources, and it provides references where you can find additional information.

This section includes the following topics:

◆ “E-Lab Interoperability Navigator” on page 9 ◆ _{“Support Summary” on page 10}

◆ “Connectivity requirements” on page 15

◆ _{“PowerPath Migration Enabler support” on page 15} Table 1 PowerPath multipathing: fixed problems

Description Found in Version Fixed in Version 384897

On RHEL 5.3 server (x86_64), upgrading PowerPath in a boot-from-SAN configuration shows error messages.

5.3 5.6 P01

376255

emcp_mond always starts without -S option even when snmpd is configured on the RHEL host.

5.6 5.6 P02

358815, 359057, 361734

Upgrading PowerPath directly from versions prior to 5.1.x and earlier to version 5.3 SP1 P02 fails. The upgrade fails because PowerPath Linux 5.3 SP1 P02 uses the powermt version format=legacy command that is not available on older versions.

5.3 SP1 P02 5.6

342843

Starting PowerPath Linux 5.3 SP1 P01 HF01 b001 throws a warning

about an extra line in /etc/modprobe.conf.pp. The warning is: modprobe: WARNING: /etc/modprobe.conf.pp line 7: ignoring bad line starting with 'ffffffff80154d70

(9)

E-Lab Interoperability Navigator

For interoperability information, such as information about the hardware, software, and networked storage components that are tested and compatible with both EMC storage systems and third-party storage systems, refer to the E-Lab Interoperability Navigator, available on the Powerlink website. It also includes information about supported host models, operating system revisions, host bus adapters, and connectivity devices.

Note:The information in E-Lab Interoperability Navigator takes precedence over the information in this release notice in case of inconsistency.

The E-Lab Interoperability Navigator is available in two formats:

◆ The E-Lab Interoperability Navigator link is a web-based,

searchable database of configuration information. Select

Software Support Wizardto view support information for PowerPath and EMC arrays.

◆ _{The PDFs and Guides tab (within E-Lab Interoperability}

Navigator) lets you view support information in Adobe PDF format. Use this format to view support information for PowerPath and third-party arrays.

(10)

Support Summary

Table 2 on page 10summarizes support for PowerPath, PowerPath Migration Enabler, and PowerPath Encryption with RSA.

Table 2 Support summary (page 1 of 3) Support

category Technology PowerPath Migration Enabler

PowerPath Encryption1

Cluster environments

Veritas Cluster Server (VCS)2 Yes Yes

Note: PowerPath

Migration Enabler User Guide provides

details of a VCS environment and the migration procedure.

Yes

File systems EXT2, EXT3

EXT4 (RHEL 6.0, and Oracle Linux 6.0 and 6.1 only)

(11)

Host operating systems

RHEL 5.0 to 5.4 Yes Yes No

RHEL 5.5 to 5.6 Yes Yes Yes

RHEL 6.0 Yes Yes

Note: Native devices are not supported.

Yes

Asianux 3.0 GM, SP1, SP2, SP3 Yes Yes No

Oracle Linux 5.1–5.5 Yes Yes No

Oracle Linux35.6

Note: PowerPath 5.6 P01 only.

Yes Yes

No

Oracle Linux35.7

Note: PowerPath 5.6 P02 only.

Yes Yes

No

Oracle Linux36.0 and 6.1 Note: PowerPath 5.6 P01 only.

Yes Yes

No

Host software

Solutions Enabler 6.5.3 or later for Open Replicator Yes Yes N/A Solutions Enabler 6.5.3 or later for TimeFinder/Clone

Minimum required disk space

120 MB

Note: This disk space is the total value required for PowerPath, Migration Enabler, and PowerPath Encryption.

Yes Yes Yes

(12)

Physical and Virtual Storage systems

EMC storage systems2 Yes Yes Yes

EMC Invista 2.3 and later Yes Yes Yes

EMC VPLEX with GeoSynchrony 5.0.x EMC VPLEX with GeoSynchrony 4.x

Note: The information in EMC Simple Support Matrix for EMC VPLEX and GeoSynchrony, available on Powerlink, takes precedence over the information in this release notice.

Yes Yes4 Yes

Third-party storage arrays2 Yes Yes4 Yes

Protocol

Fibre Channel Yes Yes Yes

iSCSI Yes Yes4 Yes

FCoE Yes Yes4 Yes

RKM

RSA Key Manager (RKM) Appliance version 2.7 SP1 • Requires RSA hot fix KMA-876 to support

multi-clusters across distance.

• RKM server supports 1000 Identities, which is equivalent to PowerPath hosts.

N/A N/A Yes

Virtually provisioned (thin) devices

Thin device support requires:

• Symmetrix Enginuity Operating Environment 5773 or later.

• VNX OE and CLARiiON with FLARE version 04.28.000.5.5xx or later and the Virtual Provisioning enabler.

Yes Yes Yes

Volume managers

Veritas Volume Manager (VxVM)2

Note: Not supported on Oracle Linux 5.6, 6.0, and 6.1.

Yes Yes Yes

Linux LVM2 Yes Yes Yes

1. x86_64 only

2. Refer to the EMC E-Lab Interoperability Navigator for details 3. Only the UEK kernels are supported

4. Host Copy only

(13)

Supported Linux distributions

Table 3 on page 13provides a quick overview of each supported kernel and its corresponding PowerPath release.

Kernel support Table 4 on page 13lists the supported Linux kernels.

Table 3 Supported Linux distributions PowerPath Release RHEL 4.2 -4.8 RHEL 5.0 -5.6 RHEL 6 SLES 10 SP2 - 10 SP4 SLES 11 -11 SP1 Oracle Linux 5.6 Oracle Linux 5.7 Oracle Linux 6.0 - 6.1 5.6 P02 No No No No No No Yes No 5.6 P01 No No No No No Yes1 No Yes1 5.6 No Yes Yes No No No No No

1. UEK kernels only.

Table 4 PowerPath 5.6 supported kernels (page 1 of 2)

Distribution1 Architecture Minimum kernel and kernel type

RHEL 6 x86 kernel- 2.6.32-71.el6.i686

x86_64 kernel- 2.6.32-71.el6.x86_64 RHEL 5.6 x86 kernel-2.6.18-238.el5.i686 kernel-xen-2.6.18-238.el5.i686 kernel-PAE-2.6.18-238.el5.i686 x86_64 kernel-2.6.18-238.el5.x86_64 kernel-xen-2.6.18-238.el5.x86_642 RHEL 5.5 x86 kernel-2.6.18-194.el5.i686 kernel-xen-2.6.18-194.el5.i6862 kernel-PAE-2.6.18-194.el5.i686 x86_64 kernel-2.6.18-194.el5.x86_64 kernel-xen-2.6.18-194.el5.x86_64 RHEL 5.4 x86 default-2.6.18-164.el5 PAE-2.6.18-164.el5 xen-2.6.18-164.el5 x86_64 default-2.6.18-164.el5 xen-2.6.18-164.el5

(14)

Storage system configuration

Before you install PowerPath, set up connections between a storage system and a host. The EMC Host Connectivity Guide for Linux describes the features and setup procedures for host interfaces to EMC Symmetrix, VNX OE and CLARiiON, Invista, and VPLEX systems. For information on setting up connections for third-party storage systems, refer to your vendor’s documentation.

Refer to the E-Lab Interoperability Navigator on Powerlink for supported EMC and third-party storage systems and firmware versions. RHEL 5.3 x86 default-2.6.18-128.el5 PAE-2.6.18-128.el5 xen-2.6.18-128.el5 x86_64 default-2.6.18-128.el5 xen-2.6.18-128.el5 RHEL 5.2 x86 default-2.6.18-92.el5 PAE-2.6.18-92.el5 xen-2.6.18-92.el5 x86_64 default-2.6.18-92.el5 xen-2.6.18-92.el5 RHEL 5.1 x86 default-2.6.18-53.el5 PAE-2.6.18-53.el5 xen-2.6.18-53.el5 x86_64 default-2.6.18-53.el5 xen-2.6.18-53.el5 Oracle Linux 5.6 x86_64 uek-2.6.32-100.26.2.el5 Oracle Linux 5.7 x86_64 uek-2.6.32-200.13.1.el5uek Oracle Linux 6.0 x86_64 uek-2.6.32-100.28.5.el6 Oracle Linux 6.1 x86_64 uek-2.6.32-100.34.1.el6uek

1. Refer to the E-Lab Interoperability Navigator for the supported kernel revisions within this update/service pack.

2. On Xen kernel, PowerPath is supported only on the Hypervisor; and, not on the guests. Table 4 PowerPath 5.6 supported kernels (page 2 of 2)

(15)

CLARiiON support CLARiiON customers receive PowerPath with the CLARiiON Utility Kits that ship with CLARiiON CX, CX3, CX4, and CX5-series storage systems. This version of PowerPath, referred to as PowerPath SE, provides basic failover for single HBA host configurations without the use of a license key. Important Information About PowerPath SE contains more information on the CLARiiON configurations supported by PowerPath SE.

Connectivity requirements

Install HBAs, supported firmware versions, and other network components using the manufacturer’s directions and the settings specified in the E-Lab Interoperability Navigator. Using improper settings can cause erratic failover behavior or extended response time for system I/O.

PowerPath Migration Enabler support

This section includes support information for PowerPath Migration Enabler.

Topics include:

◆ “Migration scenarios” on page 15

Migration scenarios Table 5 on page 15describes supported migration scenarios for PowerPath Migration Enabler.

Table 5 Supported migration scenarios (page 1 of 2)

Source logical unit Target logical unit Technology Objects

Pseudo-device name Pseudo-device name Invista Encapsulation Host Copy — TimeFinder/Clone Open Replicator Requires Solutions Enabler 6.5.3 or later

(16)

Native-device name1 Pseudo-device name Invista Encapsulation Host Copy2 TimeFinder/Clone Open Replicator

—

Thick plaintext Thin plaintext Host Copy2

TimeFinder/Clone Open Replicator Requires • Symmetrix Enginuity Operating Environment 5773 or later on the Symmetrix DMX series arrays • Symmetrix Enginuity Operating Environment 5874 SR on the VMAX series arrays • VNX OE and CLARiiON FLARE version 04.28.000.5.5xx or later and the Virtual Provisioning enabler

Migration Enabler detects thin devices by default and preserves the thin device allocation savings. Thin plaintext Thick plaintext

Thin plaintext device Thin plaintext device

Thick plaintext device Thick plaintext device Host Copy2 TimeFinder/Clone Open Replicator Encrypted pseudo-device name Encrypted pseudo-device name

Host Copy2 PowerPath Encryption uses the Host Copy technology to move data to and from encrypted devices. Encrypted pseudo-device

name

Plain text pseudo-device name

Plaintext pseudo-device name Encrypted pseudo-device name

1. Migrations between pseudo devices is supported on all platforms that support PowerPath Migration Enabler. However, migrations from native devices to pseudo devices is supported only on RHEL 5.x.

2. On Host Copy, migrations are independent of the Symmetrix, CLARiiON, or other operating environments. Table 5 Supported migration scenarios (page 2 of 2)

(17)

Known problems and limitations

This section describes known problems and limitations in PowerPath Version 5.6 and its minor releases for Linux. Each table indicates the problem description, workaround, and the version in which the problem was discovered.

◆ _{“Known problems” on page 17} ◆ _{“Limitations” on page 24}

Known problems

This section includes the following tables:

◆ _{“PowerPath multipathing” on page 17}

◆ _{“Known interoperability problems” on page 21} ◆ _{“PowerPath Migration Enabler” on page 23}

◆ _{“PowerPath Encryption with RSA: Known problems” on page 24} PowerPath

multipathing

Table 6 on page 18shows the known problems in PowerPath multipathing.

(18)

Table 6 PowerPath multipathing: known problems (page 1 of 3)

Description Workaround

Found in version 388072

While installing PowerPath 5.6 on RHEL 6.2, the following error message is shown:

emcp module is older than RHEL 6.2 ... applying fixups

No work-around. It is safe to ignore the message.

5.6

368200

Boot from SAN not supported on Oracle Linux 5.6 and 5.7 UEK. This issue is documented in EMC Knowledgebase Solution emc270933 and in Oracle Linux Bugzilla 12499

None. 5.6

367442

Oracle Linux 5.6 (kernel-uek-2.6.32-100) does not show correct information during target cable pull in a QLogic iSCSI infrastructure.

The "powermt display dev=all" command shows paths as alive while the target cablepull is done against the owner SP.

None 5.6

363943

Data corruption observed on source, target, or both after LVM operations (striping, mirroring, or snapshots) when PowerPath Encryption is in use.

This issue is documented in EMC Knowledgebase Solution emc266117.

Do not use PowerPath encryption if you plan to use LVM striping, mirroring, and/or snapshots.

5.5

356395

After upgrading from RHEL 5.5 to RHEL 6, and from PowerPath 5.5 to PowerPath 5.6, warning messages about configuration files appear. These warning messages appear only when starting PowerPath for the first time.

No action is required. 5.6

355935

The PowerPath startup script activates LVM Volume Groups that were previously inactive. This issue is documented in EMC Knowledgebase Solution emc188678.

Add the tag tag to a physical volume, volume group, or a logical volume.

5.6

343806

Unlicensed VPLEX LUNs set to BasicFailover policy, show as Active in the CLI. All but two paths should show as unlicensed.

None 5.5

342292

Paths may not recover from front end failure in certain scenarios.

Run the following command for the HBA to rediscover the remote ports:

# echo "1" > /sys/class/fc_host/host<host no>/issue_lip

(19)

336725

During a SP Hang, Call Trace messages are logged in the log file. After the SP comes up, a few paths remain dead even after a powermt restore.

Perform the following steps as a workaround: 1. Execute the following command for all the

dead paths: # echo running >

/sys/block/<sda>/device/state 2. Execute the powermt restore command.

5.5

334723

For those installations booting from R2 Symmetrix devices only, PowerPath uses the INQ tool to infer SRDF pairs from system native devices information. This INQ tool requires a system semaphore sets threshold to be increased. The requirement is the same as described in Solutions Enabler documentation, Refer to “Semaphores Requirement” in the EMC Solutions

Enabler Installation Guide for additional information.

None 5.5

333834

On a RHEL5 boot-from-SAN setup, if the initrd image is recreated after a PowerPath installation, and if the native device name of the root disk changes, then the host will not boot up. This issue is documented in EMC Knowledgebase Solution emc249231.

After PowerPath's installation on any RHEL host, perform the following steps:

1. Make a copy of the original ramdisk image found in /boot folder. Make sure that the LVM filter in the image accepts all devices.

[root@libl044 ~]# cp /boot/ initrd-2.6.18-194.el5.img

/boot/initrd-2.6.18-194.el5.img.original 2. Create a new entry in /boot/grub/menu.lst

file with the 'original' ramdisk image created in step 1 above.

Now if the issue is ever encountered, then this new grub entry can be selected so that the host can boot. Then the following needs to be done so that the host can boot properly on subsequent reboots:

a. Identify the new native device name of the root device.

b. Recreate the default ramdisk image. 3. Recreate the default ramdisk image. 4. Reboot the host.

5.5 Table 6 PowerPath multipathing: known problems (page 2 of 3)

Found in version

(20)

333231

After rebooting an Invista switch, one of the native device paths fails to come back online.

1. Run the following command for all the dead paths:

echo running >

/sys/block/<sda>/device/state 2. Run the following command: powermt restore

5.5

326019

In the /proc/diskstats file, IO statistics are not updated properly on partition devices for native paths.

None 5.5

310459

Powermt load generates warning messages when there are dead paths or if the native device names get changed after failover.

None 5.3 SP2

308967

Running the powermt display every=seconds when a path has failed and then restored may continue to display UNKNOWN.

Stopping the powermt display command and then starting a new session will show the updated information.

5.3 SP2

281284

A file system cannot be mounted after a LUN trespass and then a host reboot. PowerPath does not update the operating system partition table for the LUN because the partition table doesn’t contain entries for passive paths.

Run blockdev -rereadpt on the device after the host reboot.

5.3

269464, 268353

LCC Card & Disk Pull related issues: Paths toggle between dead and alive states before being marked dead.

If a rare situation does occur where the LUN toggles between dead and alive state continuously, a powermt restore command can be run to mark the device as dead.

5.1 Table 6 PowerPath multipathing: known problems (page 3 of 3)

Found in version

(21)

Known interoperability problems

Table 7 on page 21summarizes the known interoperability problems that affect PowerPath.

Table 7 Known interoperability problems (page 1 of 2)

Seen in version 366796

Error message is shown with LVM snapshots when the dmsetup table dm devicecommand is run after starting either PowerPath or its host. Different format expected for the device-mapper script on RHEL6, SLES 11, or SLES 11 SP1 causes this error. This issue is documented in EMC Knowledgebase Solution emc268701.

1. Visit the EMC Knowledgebase Solution emc268701.

2. Download the

pp_reset_dm_deps.shscript from the Knowledgebase Solution.

3. Replace the same script in the

/etc/opt/emcpowerdirectory with the downloaded script.

4. Follow the relevant procedure in the Knowledgebase Solution.

5.5

356286, 355111

In non-SRDF setup, starting PowerPath 5.6 consumes more than the expected time. This issue is found only when VPLEX or Invista devices are connected to the host.

Replace the pp_inq script with a script that contains ‘exit 0’.

5.6

353911

On RHEL 6.0 and 6.1, because each calls to the udevadm settle command requires three minutes to complete, uninstalling PowerPath consumes a longer time.

Install the following Selinux patches: selinux-policy-targeted-3.7.19-93.el6.noarch libselinux-python-2.0.94-5.el6.x86_64 selinux-policy-mls-3.7.19-93.el6.noarch libselinux-2.0.94-5.el6.x86_64 libselinux-devel-2.0.94-5.el6.x86_64 selinux-policy-minimum-3.7.19-93.el6.noarch selinux-policy-3.7.19-93.el6.noarch libselinux-utils-2.0.94-5.el6.x86_64 5.6 337328, 340760

An issue has occurred on RHEL 5.5 with both Solutions Enabler 7.1.0 and 7.1.1. There is a problem releasing the locked semaphores. When running symcfg discover, the following error message is shown: The gatekeeper device (while using the Base Daemon) has an error.

Upgrade to Solution Enabler V7.1.1.26 with T7.2.0.507.

5.5

333917

When migrating data from a thick to a thin device with

TimeFinder/Clone on a Symmetrix VMAX with Enginuity 5874, the powermig query command displays an inaccurate value for Percent InSync. This occurs because the Percent InSync value includes the

(22)

355022, 353108, 357284

On RHEL 6.0, there are slow path warnings and errors in log files for each device when restoring reconnected paths.

You can ignore the error messages. 5.6

336484

In a Veritas Cluster Server setup with two or more nodes, the pseudo names of the shared devices must be the same across all the nodes in the cluster.

When the pseudo names are not the same, perform the following steps:

1. Run the emcpadm export_mappings command on the shared VxVM emcpower device.

2. Delete the disk.info and disk.info.old from the /etc/vx directory.

3. Import the PowerPath mapping from the other host running the emcpadm import_mappings command. 4. Perform vxdisk scandisks. An error should not occur.

5.5

285139

When running scandisks for Oracle ASM volumes on PowerPath 5.1.x, the host hangs. This issue is seen with a larger number of volumes.

The workaround is to execute the asmscan.sh script. This issue is documented in the EMC Knowledgebase solution emc198046.

5.1 Table 7 Known interoperability problems (page 2 of 2)

Seen in version

(23)

PowerPath Migration Enabler

Table 8 on page 23shows the known problems in PowerPath Migration Enabler.

Table 8 PowerPath Migration Enabler: known problems

Found in version 359574

Running the vxdisk scandisks command after a Host Copy migration at VxVM controlled devices shows an error message; in addition, the command does not recognize newly added LUNs.

1. Remove the migrated LUNs from VxVM control.

2. Add the new LUNs on the host, if required.

3. Rescan VxVM to get new LUNs and migrated LUNs in VxVM control.

Hint:Scanning the VxVM environment or a planned reboot results in application downtime. Performing both of them together could prevent additional application downtime.

5.6

358794, 358464

In the Open Replicator and TimeFinder/Clone migrations on RHEL6 with ext4 filesystems, the powermig commands show the following error message upon a host crash:

The SYMAPI database file is invalid or corrupted

1. Replace the corrupted SYMAPI database file with valid database file: # mv /var/symapi/db/symap i_db.bin /var/symapi/db/symap i_db.bin.old

2. To use the new SYMAPI database, run:

# symcfg discover

5.6

313430

With devices involved in an Open Replicator migration, when all the ports of VNX OE and CLARiiON are disabled, the paths of the Symmetrix devices involved in the migration might also go dead.

None 5.3 SP1

288991

When setting up a TimeFinder/Clone migration from a standard device to meta device, the following error message gets displayed: PPME_SYMCLONE error(182): A configuration mismatch was detected among members of your META devices.Any target Meta device

selected results in the error.

(24)

PowerPath Encryption with RSA

Table 9 on page 24shows the known problems in PowerPath Encryption with RSA.

Limitations

This section describes limitations by product:

◆ _{“PowerPath Multipathing” on page 24} ◆ “PowerPath Migration Enabler” on page 25 ◆ _{“PowerPath Encryption with RSA” on page 25} PowerPath Multipathing

PowerPath 5.6 P02 does not support the following:

◆ Boot from SAN on Oracle Linux 5.7.

◆ _{Veritas Volume Manager on Oracle Linux 5.7}

PowerPath 5.6 P01 does not support the following:

◆ Boot from SAN on Oracle Linux 5.6.

◆ _{Veritas Volume Manager on Oracle Linux 5.6, 6.0, and 6.1} Table 9 PowerPath Encryption with RSA: Known problems

Found in version 363943, 365713

Although the source data is not corrupt, mounting the snapshot, striped, or mirrored logical volume on an encrypted LUN corrupts some files on the source, target, or both. However, the error is not logged.

This issue is documented in EMC Knowledgebase Solution emc266117.

None 5.5

353758

Logical Volumes on an encrypted device do not get activated when uninstalled PowerPath is reinstalled and encryption is activated.

Manually activate the Logical Volumes on encrypted devices after reinstalling PowerPath.

5.6

312559/312287

Automount of encrypted devices and Logical volumes created out of encrypted devices may not happen on hosts with /usr as a separate partition. This is because PowerPath encryption requires few libraries such as libstdc++ which are available only in /usr partition and these may not be available when PowerPath starts during system bootup.

Manually mount the encrypted devices after the boot. This workaround is required only in configurations where the /usr partition is in a different disk or volume.

(25)

This section includes the limitations in PowerPath Migration Enabler.

◆ _{The following limitations apply only to Host Copy migrations:}

Host Copy supports migrating devices that exist on different transports (Fibre Channel and iSCSI software initiator) or iSCSI software initiator.

However, when migration involves iSCSI devices either as source, target, or both, host reboots are not supported. If a reboot does occur, the migration session must be aborted and then restarted.

Reboots are not supported with migrations involving iSCSI devices to or from encrypted devices. (Host Copy is the underlying technology used with PowerPath Encryption).

This section includes the limitations in PowerPath Encryption with RSA:

◆ _{PowerPath 5.6 P02 does not support PowerPath Encryption on}

Oracle Linux 5.7

◆ PowerPath 5.6 P01 does not support PowerPath Encryption on

Oracle Linux.

◆ _{LUN shrink is not supported with PowerPath Encryption}

enabled.

A LUN shrink operation performed with encrypted devices may lead to a Data Unavailable/Data Loss scenario.

Technical notes

This section includes technical notes on the following topics, which are arranged as follows:

◆ _{“PowerPath multipathing” on page 26} ◆ “PowerPath Migration Enabler” on page 33 ◆ _{“PowerPath Encryption with RSA” on page 34}

(26)

◆ “PowerPath and VMAX/VMAXe series devices” on page 26 ◆ _{“PowerPath and VNX series devices” on page 26}

◆ “Setting periodic_autorestore to off still restores dead paths” on page 27

◆ _{“Paths not released in a cluster or LVM environment” on page 27} ◆ “Placing Celerra iSCSI devices under PowerPath control” on

page 27

◆ _{“PowerPath and the CLARiiON admsnap utility” on page 28} ◆ _{“Supporting more than 256 storage devices” on page 28} ◆ _{“Symmetrix Enginuity Operating Environment” on page 30} ◆ _{“VNX OE and CLARiiON FLARE Operating Environment” on}

page 30

◆ _{“iSCSI devices” on page 31}

◆ _{“Running the powermt load command may give false warning} messages” on page 31

◆ _{“Mode not reflecting properly across a reboot” on page 31} ◆ _{“Mount option in the /etc/fstab” on page 32}

◆ _{“Expanding the file system on a pseudo-device” on page 32} ◆ _{“PowerPath licenses in a CLARiiON AX and CX configuration”}

on page 32

◆ _{“PowerPath Viewer support” on page 32} PowerPath and VMAX/VMAXe series devices

VMAX and VMAXe devices are managed under the symm storage class. This means that in powermt display, any VMAX or VMAXe devices you may have under PowerPath management appear as Symmetrix devices. Similarly, the default and licensed failover and load-balancing policies are bf for unlicensed devices and SymmOpt for licensed devices.

PowerPath and VNX series devices

VNX OE devices are managed under theclariionstorage class. This means that in powermt display, any VNX OE devices that you may have under PowerPath management appear as CLARiiON devices.

(27)

Similarly, the default unlicensed and licensed failover and load-balancing policies are the same for VNX OE devices as for CLARiiON; that is, Basic Failover for unlicensed devices and CLARopt for licensed devices. VNX devices behave like CLARiiON devices on PowerPath with respect to multipathing and

failover/failback.

VNXe devices are managed under the generic storage class. In powermt display, any VNXe devices that you may have under PowerPath management appear as Celerra devices. The default unlicensed failover and load-balancing policy is Basic Failover; for licensed devices, the policy is Adaptive. More information is available on the VNX OE Storage System Support website (www.emc.com/vnxsupport).

Setting periodic_autorestore to off still restores dead paths

On some Linux platforms, when the powermt set

periodic_autorestore commandis set to off, PowerPath will continue to test and restore dead paths. This is an expected behavior on Oracle Linux Versions 5.6, 5.7, 6.0, and 6.1, and RHEL 6.0 kernels.

Paths not released in a cluster or LVM environment

In a cluster or LVM environment, host software may hold references to PowerPath or native devices. In such a situation, PowerPath cannot release one or more paths despite the device is removed or renamed. Reboot PowerPath for the host software to release these references.

Placing Celerra iSCSI devices under PowerPath control

PowerPath treats EMC Celerra iSCSI devices as generic devices. Enable generic Loadable Array Module (LAM) support so that PowerPath can recognize and manage Celerra iSCSI devices. Note:For VNXe devices same procedure is applicable, including generic Loadable Array Module (LAM) support.

Managing Celerra iSCSI targets

To place Celerra iSCSI devices under PowerPath control: 1. Add the following line to the /etc/emc/mpaa.lams file:

(28)

3. Run powermt config.

4. Run the /etc/init.d/PowerPath stop and /etc/init.d/PowerPath

startcommand sequence to restart PowerPath or reboot the host.

Unmanaging Celerra iSCSI targets

To remove Celerra iSCSI devices from PowerPath control: 1. Remove the following line from the /etc/emc/mpaa.lams file:

managed:generic:EMC:Celerra 2. Run powermt init.

3. Run powermt config.

4. Run the /etc/init.d/PowerPath stop and /etc/init.d/PowerPath

startcommand sequence to restart PowerPath or reboot the host.

PowerPath and the CLARiiON admsnap utility

Take note of the following if you use the CLARiiON admsnap utility with PowerPath devices.

◆ _{For all versions of the admsnap utility, set the}

PP_SHOW_CLAR_OWNING_SPenvironment variable to false to suppress the display of default and current SP data:

PP_SHOW_CLAR_OWNING_SP=false

◆ For admsnap utility version 2.4.0.0.3 or less:

• Set the PP_DEFAULT_STORAGE_SYS environment variable to VNX OE and CLARiiON to restrict the class of devices displayed by the powermt utility to VNX OE and CLARiiON devices:

PP_DEFAULT_STORAGE_SYS=CLARiiON

• Use a native PowerPath name (for example, /dev/sde) to start or activate an admsnap session when a file system is mounted on a PowerPath device. You cannot use a PowerPath pseudo device name (for example, /dev/emcpowere) to start or activate a session when a file system is mounted on a PowerPath device.

Supporting more than 256 storage devices

Complete the following steps to support more than 256 storage devices on a host.

(29)

Emulex HBAs

If you using Emulex HBAs, set the lpfc_max_luns parameter to 1024,

2048, or 4096.

QLogic HBAs

If you using QLogic HBAs, change the system parameters under

/sys/module/scsi_mod/max_lunsand max_report_luns to the recommended value.

For more information, refer to the EMC Host Connectivity Guide for Linux or to the vendor website.

Making the parameter settings permanent across reboot

To make the parameter settings permanent across reboot on Emulex or QLogic HBAs:

On RHEL 5.x

1. Edit the /etc/modprobe.conf file and set the lpfc_max_luns parameter to 1024, 2048, or 4096.

2. Recreate the initrd.

3. Point the initrd to the new initrd when booting. On RHEL 6.x

1. Create the lpfc.conf file in the /etc/modprobe.d/ directory. 2. Edit the file and set the lpfc_max_luns parameter to 512. 3. Recreate the initramfs by running the dracut -f command. 4. Reboot the host.

For more information, refer to the EMC Host Connectivity Guide for Linux or to the vendor website.

Unmanaging more than 256 LUNs causes PowerPath loading failures.

To resolve the PowerPath loading failure:

1. Type mv /etc/init.d/PowerPath /etc/init.d/PowerPath.orig 2. Restart the host.

3. Remove /etc/emc/mpaa.excluded.

4. Edit /etc/modprobe.conf.pp to remove the excludedvolumes module parameter and its associated arguments.

(30)

6. Type /etc/init.d/PowerPath start. 7. Unmanage the devices (up to 256).

Configuring 256 devices in a boot-from-SAN environment

In a boot-from-SAN SLES environment, PowerPath configures only 256 device paths, though more device paths are available to the system.

Perform the following:

1. Run /sbin/udevstart to repopulate the device directory. 2. Run powermt config.

3. Run chkconfig boot.udev on to configure udev to start up automatically on subsequent reboots.

4. Run chkconfig boot.udev to confirm the change.

Symmetrix Enginuity Operating Environment

Take note of the following issues regarding the Symmetrix Enginuity Operating Environment.

Enginuity Operating Environment 5568 reservation and pre-emption commands

The Reservation and pre-emption commands in Enginuity

Operating Environment 5568 are not working according to the SCSI-3 specification. This issue is seen both with PowerPath and without PowerPath on a host. This is not a PowerPath issue.

Enginuity Operating Environment 5773 and VxVM

With Symmetrix Enginuity Operating Environment 5773 and VxVM, Symmetrix patch 5773.130.90 or later is required. This patch fixes an issue where the vxfentsthdw utility fails while testing a SCSI-3 persistent group reservation enabled LUN.

VNX OE and CLARiiON FLARE Operating Environment

Take note of the following issue regarding the VNX OE and CLARiiON FLARE Operating Environment.

FLARE Operating Environment 04.28 and over-provisioning

After over-provisioning the thin pool on a VNX OE and CLARiiON array with FLARE version 04.28.000.5.706, the hosts connected to the VNX OE and CLARiiON receives SCSI related errors and does not see all the thin LUNs after a host reboot. This is a VNX OE and CLARiiON issue that has been fixed in FLARE version 04.29.

(31)

iSCSI devices

Take note of the following issues regarding native iSCSI devices using the software initiator in a PowerPath environment.

Configuring iSCSI to start on host boot

EMC recommends configuring your iSCSI initiator service to start automatically when the host boots. Run chkconfig to enable the iSCSI service.

Note:If you stop PowerPath and then the device configuration changes, when you restart PowerPath you may see a message that PowerPath failed to start. You can ignore this message.

Stopping iSCSI on a PowerPath host

Always stop PowerPath before stopping iSCSI on a host with iSCSI devices under PowerPath control.

Note:Ensure that anything that has an iSCSI device open has closed the iSCSI device before shutting down iSCSI. This includes file systems, volume managers, and user applications.

To stop iSCSI on a PowerPath host: 1. Type /etc/init.d/PowerPath stop. 2. Type /etc/init.d/iscsi stop.

Adding or removing iSCSI devices

"Dynamic LUN addition and removal" in the EMC PowerPath for Linux Installation and Administration Guide provides more information on adding or removing iSCSI devices.

Running the powermt load command may give false warning messages

With iSCSI Celerra devices, running powermt load gives a "Error occurred loading saved driver state from file /etc/powermt.custom" warning message although the configuration is restored. Because the configuration is restored, ignore the warning message.

Mode not reflecting properly across a reboot

When a PowerPath load balancing and failover mode is changed, the mode may not reflect properly after the reboot. This is caused by the native device name sometimes changing during the reboot, creating an incorrect configuration and is Linux operating system behavior.

(32)

Mount option in the /etc/fstab

RHEL 5.x and RHEL 6.x PowerPath devices should use the _netdev mount option in the

/etc/fstabfile for both FC, FCoE, and iSCSI devices. This will ensure that fsck is run later in the boot sequence.

Expanding the file system on a pseudo-device

To expand the file system on a pseudo device, follow the steps below: Note:For encrypted devices, refer to "Expanding the encrypted LUN from the array side,” in the PowerPath 5.6 Encryption with RSA User Guide.

1. Expand the LUN on the array.

2. Unmount the file system if it is mounted.

3. Run blockdev --rereadpt /dev/<Pseudo device> to re-read the partition table of the pseudo device.

4. Follow the operating system’s recommended steps to resize the file system: resize2fs –p /dev/<Pseudo device> for the ext2,

ext3, or ext4 file system.

5. Run mount /dev/<Pseudo device> <Mount point>.

PowerPath licenses in a CLARiiON AX and CX configuration

When running PowerPath without a license on a host attached to both CLARiiON AX and CX arrays, PowerPath does not display a warning about the missing license for the CX array. This behavior may be unexpected as PowerPath does display a missing license warning when connected to CX arrays when no AX array is present. Without a license, only the AX array has full PowerPath functionality; the CX array will not have failover support.

In a configuration with both CLARiiON AX and CX arrays, ensure a valid license is present for the CX array by entering emcpreg -list.

PowerPath Viewer support

PowerPath 5.6 and its minor releases for Linux are supported on EMC PowerPath Viewer. PowerPath Viewer can monitor the status of hosts running PowerPath 5.6 for Linux environments.

EMC PowerPath Viewer is a centralized monitoring utility that provides a consolidated display of events, and allows you to view and monitor up to 500 PowerPath hosts through a graphical user interface (GUI). With EMC PowerPath Viewer, you can view hosts,

(33)

host groups, LUNs, individual paths to each LUNs, and buses. PowerPath Viewer also provides email alerts about any changes in the status of PowerPath devices.

PowerPath Viewer includes two components: PowerPath Viewer Console, which is the interface that displays information and alerts about PowerPath custom-tailored devices shown in windows and panes; and the PowerPath Management Component, which is the host-based software that monitors host, LUNs, data path, and bus events and sends information and alerts to the Viewer Console over IP.

PowerPath Viewer is available as a separate download in the PowerPath software downloads section of Powerlink.

The PowerPath Viewer 1.0 and Service Pack Releases Release Notes, available on Powerlink, provides more information.

◆ “Source/target LU faults with kexec service” on page 33 ◆ _{“Symmetrix gatekeeper devices” on page 33}

Source/target LU faults with kexec service

When kexec is enabled, Host Copy migrations with PowerPath Migration Enabler result source/target LU faults. Host that could not do a full reboot causes these faults.

Therefore, when performing a Host Copy migration, if you have the kexec service running, type # chkconfig -s kexec off to disable it.

Symmetrix gatekeeper devices

Logical units involved in a migration should not be used as

Symmetrix gatekeeper devices. To ensure that migration devices are NOT used as gatekeepers, choose at least one non-migration device and add it to the SYMAPI gkselect file (multiple gatekeeper devices can be added). This ensures that SMAPI will only use those devices as gatekeepers. The EMC Solutions Enabler Symmetrix Base

Management CLI Product Guide contains more information about gatekeeper devices.

(34)

◆ “Performance in migrations with encrypted devices” on page 34 ◆ _{“Compression issues with encrypted data for RecoverPoint” on}

page 34

◆ “BCV device encryption” on page 34 Performance in migrations with encrypted devices

Migrating data to or from encrypted devices increases the CPU load on a PowerPath Encryption host since it must handle the processing load of encrypting or decrypting the data that is being migrated in addition to the normal application processing load. For information about monitoring and controlling the performance of migrations, refer to the PowerPath Migration Enabler User Guide.

Compression issues with encrypted data for RecoverPoint

PowerPath Encryption with RSA works with fabric-based SANTap and RecoverPoint running on a VNX OE and CLARiiON storage device. If RecoverPoint is used for remote replication, data encryption will make compression ineffective and hence a higher bandwidth will be required for encrypted devices that are being remotely replicated.

BCV device encryption

The following step overcomes the problem of BCV device’s inability to get encrypted after the split operation with the encrypted standard device.

Note:After a TimeFinder operation, updating of the BCV device encryption state is necessary.

Run powervt update -dev <device_to_be_updated> to re-key the BCV device. Once the command is executed, the device would become encrypted and will be usable.

(35)

Documentation

Table 10 on page 35lists the PowerPath documentation set; all manuals are available from EMC Corporation.

Localized versions of the EMC PowerPath for Linux Installation and Administration Guide are available in French, German, Italian, Japanese, Korean, Portuguese, simplified Chinese, and Spanish languages.

PowerPath/VE for VMware vSphere is covered in the PowerPath for VMware vSphere documents, available on Powerlink.

Electronic versions of all PowerPath manuals are available on the Powerlink website. These manuals are updated periodically, and the updated manuals are posted on the Powerlink website.

Related Documentation

The following are related documentation for Symmetrix, and VNX OE and CLARiiON storage systems.

Table 10 PowerPath Family documentation set Part Number Title

PowerPath Family

300-006-627 EMC PowerPath Family Version 5.2, 5.3, 5.5, and 5.6 Product Guide

300-011-783 EMC PowerPath Version 5.6 CLI and System Messages Reference

300-011-782 EMC PowerPath Family for Linux Version 5.6 and Service Pack Releases Release Notes (this document)

300-011-781 EMC PowerPath for Linux Version 5.6 Installation and Administration Guide

300-011-785 EMC PowerPath Migration Enabler Version 5.6 User Guide

(36)

Symmetrix storage systems

If your environment includes Symmetrix storage systems, refer to the following:

EMC Host Connectivity Guide for Linux, which provides basic information about the features and setup procedures for host interfaces to Symmetrix systems.

VNX OE and CLARiiON storage systems

If your environment includes VNX OE and CLARiiON storage systems, refer to the following:

◆ EMC Host Connectivity Guide for Linux, which provides basic

information about the features and setup procedures for host interfaces to VNX OE and CLARiiON systems.

◆ _{CLARiiON Support home page:}_{www.emc.com/clariionsupport} ◆ VNX OE Support home page:www.emc.com/vnxsupport ◆ _{EMC Host Connectivity Guides, which provides basic information}

about the features and setup procedures for host interfaces to VNX OE and CLARiiON systems.

Note:CLARiiON customers receive PowerPath with the CLARiiON Utility Kits that ship with CLARiiON CX- and CX3-series storage systems. This version of PowerPath, referred to as PowerPath SE, provides basic failover for single HBA host configurations without the use of a license key. The

Important Information about PowerPath SE document, available on the

Powerlink website, provides additional information on the CLARiiON configurations supported by PowerPath SE.

A subset PowerPath functions are available through the UnisphereTM application for VNX OE systems. Refer to the VNX OE Storage System Support website (www.emc.com/vnxsupport). A subset of PowerPath functions are available through the

Navisphere® and the Unisphere applications for CLARiiON systems. Refer to CLARiiON Storage-System Support website

(www.emc.com/clariionsupport).

RSA Key Manager The following documents describe the RSA Key Manager software:

◆ _{RSA Key Manager Server Release Notes}

◆ RSA Key Manager Server Administrator’s Guide

The following documents describe the RSA Key Manager appliance:

◆ _{RSA Key Manager Appliance Release Notes} ◆ RSA Key Manager Appliance Quick Start Guide

(37)

This documentation is available on the product CD.

If your environment includes other vendors’ storage systems, refer to the appropriate documentation from your vendor.

End of service dates and extended support

EMC has a standard software support duration policy which specifies that a major version will reach End of Service Life (EOSL) a minimum of 36 months following the General Availability (GA). EOSL may be followed by an Extended Support period during which customers may elect to pay an additional fee to extend their support coverage rather than migrate to a current software version.

Once a software product reaches EOSL, EMC Technical Support is no longer available under base support/maintenance agreements. Customers interested in uninterrupted support must upgrade to a current release or contract for Extended Support (ES).

Powerlink contains a list of documents that provide end-of-service and extended support information for EMC software and hardware products.

To access these documents on Powerlink: 1. Go to Powerlink.

2. Enter the following text in the Search box and click Search: EMC software release end of service life

3. Find the EMC Software Release and End of Service Life

Notificationsdocument in the results.

4. Open it and search for your product and version.

This document provides EOSL dates for EMC software products. Note:This policy is in effect for select releases and will be phased in as new versions are made available. In cases where a software release is not eligible for Extended Support, the previous policy, which specifies product support and maintenance under Continuous Coverage Product Maintenance (CCPM), terms still apply.

(38)

Software media, organization, and files

This section contains information about the PowerPath 5.6 media and files.

EMC PowerPath Version 5.6 and its minor releases for Linux is a full release available on CD and for download from the Powerlink and EMC.com websites.

Media and releases The PowerPath Version 5.6 and its minor releases for Linux software CD has the following structure:

./LINUX: pp5.5.x pp5.6.x VNX ./LINUX/pp5.5.x EMCPower.LINUX.5.5.GA.b275.tar.gz ./LINUX/pp5.5.x/rhel EMCPower.LINUX-5.5.0.00.00-275.RHEL5.i386.rpm EMCPower.LINUX-5.5.0.00.00-275.RHEL5.IA64.rpm EMCPower.LINUX-5.5.0.00.00-275.RHEL5.x86_64.rpm EMCPower.LINUX-5.5.0.00.00-275.RHEL5.PPC64.rpm ./LINUX/pp5.5.x/sles EMCPower.LINUX-5.5.0.00.00-275.SLES10SP3.i386.rpm EMCPower.LINUX-5.5.0.00.00-275.SLES10SP3.IA64.rpm EMCPower.LINUX-5.5.0.00.00-275.SLES10SP3.x86_64.rpm EMCPower.LINUX-5.5.0.00.00-275.SLES10SP3.PPC64.rpm EMCPower.LINUX-5.5.0.00.00-275.SLES11SP1.i386.rpm EMCPower.LINUX-5.5.0.00.00-275.SLES11SP1.x86_64.rpm EMCPower.LINUX-5.5.0.00.00-275.SLES11SP1.IA64.rpm EMCPower.LINUX-5.5.0.00.00-275.SLES11SP1.PPC64.rpm ./LINUX/pp5.6.x EMCPower.LINUX.5.6.GA.b143.tar.gz ./LINUX/pp5.6.x/rhel EMCPower.LINUX-5.6.0.00.00-143.RHEL5.i386.rpm EMCPower.LINUX-5.6.0.00.00-143.RHEL5.x86_64.rpm EMCPower.LINUX-5.6.0.00.00-143.RHEL6.i386.rpm EMCPower.LINUX-5.6.0.00.00-143.RHEL6.x86_64.rpm ./LINUX/pp5.6.x/oel

(39)

EMCPower.LINUX-5.6.0.01.00-005.OL56.x86_64.rpm EMCPower.LINUX-5.6.0.01.00-005.OL6.x86_64.rpm ./LINUX/pp5.6.x/ovs

EMCPower.LINUX-5.6.0.01.00-005.OVS3.x86_64.rpm ./LINUX/VNX/

PowerPath Encryption VNX Security and Compliance Suite README

Table 11 on page 39summarizes the PowerPath 5.6 package and releases.

Files For information about files added by PowerPath 5.6, refer to “Files Changed By PowerPath,” in the PowerPath 5.6 for Linux Installation and Administration Guide.

Installation

◆ _{“PowerPath Configuration Checker” on page 40} ◆ _{“Installing PowerPath multipathing” on page 40} ◆ _{“Installing PowerPath Migration Enabler” on page 40} ◆ _{“Installing PowerPath Encryption with RSA” on page 40} Table 11 PowerPath Version 5.6 for Linux package and releases

PowerPath release/description Package/Part number Build

EMC PowerPath, PowerPath Migration Enabler, and PowerPath Encryption with RSA version 5.6 for Linux software CD.

053-002-357 A01 N/A

PowerPath Version 5.6 EMCPower.LINUX.5.6.GA.b143.tar.gz b143 PowerPath Version 5.6 P01 EMCPower.LINUX.5.6.P01_b005.tar.gz b005 PowerPath Version 5.6 P02 EMCPower.LINUX.5.6.P02_b001.tar.gz b001

(40)

PowerPath Configuration Checker

PowerPath Configuration Checker (PPCC) is a software program that verifies that a host is configured to E-Lab Interoperability Navigator standards with the hardware and software required for PowerPath multipathing features (failover and load-balancing functions, licensing, and policies). PPCC is available for download on Powerlink.

Prior to installing or upgrading PowerPath, download the latest version of EMC Grab available on Powerlink and then run PPCC. This ensures that the system version used by PPCC includes the latest configuration information.

For installation information, the EMC PowerPath Configuration Checker User Guide, available on Powerlink, provides additional information.

Installing PowerPath multipathing

To install PowerPath follow the instructions in the EMC PowerPath for Linux Installation and Administration Guide, available on Powerlink. Upgrading PowerPath

PowerPath 5.6 for Linux supports the following upgrades from:

◆ _{PowerPath 5.x to 5.6} ◆ RHEL 5.x to RHEL 6.0

Installing PowerPath Migration Enabler

To install PowerPath Migration Enabler on Linux hosts:

1. If you have not done so already, install PowerPath Version 5.6. The EMC PowerPath for Linux Installation and Administration Guide provides additional information.

2. Install the PowerPath Migration Enabler license key and configure the Migration Enabler host. The EMC PowerPath Migration Enabler User Guide provides additional information.

Installing PowerPath Encryption with RSA

(41)

1. If you have not done so already, install PowerPath Version 5.6. The EMC PowerPath for Linux Installation and Administration Guide provides additional information.

2. Install the PowerPath Encryption with RSA license key and configure the Encryption host. The EMC PowerPath Encryption with RSA User Guide provides additional information.

Troubleshooting and getting help

EMC support, product, and licensing information can be obtained as follows:

Product information— For documentation, release notes, software updates, or for information about EMC products, licensing, and service, go to the EMC Powerlink website (registration required) at:

http://Powerlink.EMC.com

Technical support— For technical support, go to EMC WebSupport on Powerlink. To open a case on EMC WebSupport, you must be a WebSupport customer. Information about your site configuration and the circumstances under which the problem occurred is required.

Service packs and upgrades —You can download PowerPath service pack software from Powerlink. Determine which service packs (if any) you want to install after PowerPath, and whether those service packs have any additional installation prerequisites. To obtain service packs on Powerlink, select Support > Software Downloads

and Licensing> Downloads P-R > PowerPath for Linux.

Reporting a problem

If you find a problem in PowerPath, run the emcgrab utility, which collects system and software configuration information. Submit the generated tar file, along with any other supporting material, to EMC Customer Support.

EMC Grab 3.9 or later is required to collect information about PowerPath Encryption with RSA or Host Copy migrations. EMC Grab version 3.7 or later collects information about PowerPath Migration Enabler for Open Replicator or Invista.

(42)

You can download emcgrab from the Powerlink website. Select

Support> Product and Diagnostic Tools > Grab Utilities. Refer to the emcgrab ReadMe.txt file on Powerlink for prerequisite

information and instructions on using the utility.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF

MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

For the most up-to-date regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink.

For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are t property of their respective owners.